compilation errors with --enable-spoof-source
Hi, I am using syslog-ng 1.6.11 and trying to compile this package with ./configure --enable-spoof-source, it throws errors as below checking whether to enable Sun STREAMS support... yes checking whether to enable Sun door support... yes checking whether to enable TCP wrapper support... no checking whether to enable spoof_source support... ./configure: test: too many arguments configure: error: libnet-config not found It compiles fine without --enable-spoof-source this option. Could you do the needful. Thanks, Ravi Kumar P.
On Mon, 2007-02-19 at 13:09 -0600, Ravi Papisetti -X (rpapiset - HCL at Cisco) wrote:
Hi,
I am using syslog-ng 1.6.11 and trying to compile this package with ./configure --enable-spoof-source, it throws errors as below
checking whether to enable Sun STREAMS support... yes checking whether to enable Sun door support... yes checking whether to enable TCP wrapper support... no checking whether to enable spoof_source support... ./configure: test: too many arguments configure: error: libnet-config not found
It compiles fine without --enable-spoof-source this option. Could you do the needful.
You need libnet in order to compile syslog-ng with spoof source support. -- Bazsi
On Mon, 2007-02-19 at 16:36 -0600, Ravi Papisetti -X (rpapiset - HCL at Cisco) wrote:
Already that is installed in my m/c. Compilations went successful without this option. I understand that libnet is to compile this package.
Let us know how to check if Libnet package installation is fine in my system or not.
if libnet is installed, you should have a script called libnet-config somewhere in your path. that's what the configure script does not find. -- Bazsi
I configured syslog-ng to use the template to generate mysql INSERT statements and write to a unix pipe. I am using a shell script that reads from this pipe and replays these messages to mysql. In normal load conditions all the messages are making it to the db. It even worked fine when I pumped in 100msgs/sec. However when I sent a burst of 500msgs only around 180msgs are making it through. When I try the same rate writing to a text file (not using unix pipe), all the msgs make it through. so, it looks like the msgs are getting dropped due to the pipe overflow. Did anybody encounter the same problem? If so, do you have any suggestions to overcome this problem? When I replayed the INSERT commands using unix cat to the pipe and write it to the db using the same script, I was able to write 2500rows/sec. I thing cat call blocks. so, is the problem related to how syslong-ng writes to the pipe? thanks ramesh
I was able to solve the problem by setting log_fifo_size to 1000. ramesh Ramesh Uppuluri wrote:
I configured syslog-ng to use the template to generate mysql INSERT statements and write to a unix pipe. I am using a shell script that reads from this pipe and replays these messages to mysql. In normal load conditions all the messages are making it to the db. It even worked fine when I pumped in 100msgs/sec. However when I sent a burst of 500msgs only around 180msgs are making it through. When I try the same rate writing to a text file (not using unix pipe), all the msgs make it through. so, it looks like the msgs are getting dropped due to the pipe overflow. Did anybody encounter the same problem? If so, do you have any suggestions to overcome this problem?
When I replayed the INSERT commands using unix cat to the pipe and write it to the db using the same script, I was able to write 2500rows/sec. I thing cat call blocks. so, is the problem related to how syslong-ng writes to the pipe?
thanks ramesh
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
Hi, How would I include libnet-config path during compilation of syslog-ng. Thanks, Ravi Kumar P. From: Balazs Scheidler Sent: Tue 20-Feb-07 2:59 AM To: Syslog-ng users' and developers' mailing list Subject: RE: [syslog-ng] compilation errors with --enable-spoof-source On Mon, 2007-02-19 at 16:36 -0600, Ravi Papisetti -X (rpapiset - HCL at Cisco) wrote:
Already that is installed in my m/c. Compilations went successful without this option. I understand that libnet is to compile this package.
Let us know how to check if Libnet package installation is fine in my system or not.
if libnet is installed, you should have a script called libnet-config somewhere in your path. that's what the configure script does not find. -- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
On Wed, 2007-02-21 at 16:43 -0600, Ravi Papisetti -X (rpapiset - HCL at Cisco) wrote:
Hi,
How would I include libnet-config path during compilation of syslog-ng.
by setting the PATH environment variable or using --with-libnet=<path> configure option. -- Bazsi
On Fri, 2007-03-02 at 12:58 -0600, Ravi Papisetti -X (rpapiset - HCL at Cisco) wrote:
Hi Bazsi,
Sorry, I thought libol-0.3.18 and libnet are same. Could you tell me where can we get libnet and how do we configure.
We are working with syslog-ng.1.6.11 on Solaris 8.
libnet and libol are completely different beasts. libol is a light-weight OO framework for syslog-ng, libnet is a library to inject packets portably to the wire. libnet is used to implement spoof-source support. BTW: latest snapshots of the 2.0.x branch include spoof-source support (no release yet, however), 1.6.x is old and is going to be unsupported in the not-too-distant future. If your project is just being started, I'd suggest to start with 2.0.x instead of the old branch. -- Bazsi
On Sat, 2007-03-03 at 15:20 +0100, Balazs Scheidler wrote:
On Fri, 2007-03-02 at 12:58 -0600, Ravi Papisetti -X (rpapiset - HCL at Cisco) wrote:
Hi Bazsi,
Sorry, I thought libol-0.3.18 and libnet are same. Could you tell me where can we get libnet and how do we configure.
We are working with syslog-ng.1.6.11 on Solaris 8.
libnet and libol are completely different beasts. libol is a light-weight OO framework for syslog-ng, libnet is a library to inject packets portably to the wire.
libnet is used to implement spoof-source support.
Ops, the most important information, libnet is at: http://www.packetfactory.net/projects/libnet/ -- Bazsi
participants (3)
-
Balazs Scheidler
-
Ramesh Uppuluri
-
Ravi Papisetti -X (rpapiset - HCL@Cisco)