March 2004 - syslog-ng - lists.balabit.hu

RE: [syslog-ng]Syslog-ng Installation Problem
by Hamilton, Andrew 26 Mar '04

26 Mar '04

Well you can do that but it still won't work as you are using 0.3.9. The configure clearly is looking for something equal to or better than 0.3.13. Drew -----Original Message----- From: Rule, Ted [mailto:Ted_Rule@flextech.co.uk] Sent: Friday, March 26, 2004 6:13 AM To: syslog-ng(a)lists.balabit.hu Subject: RE: [syslog-ng]Syslog-ng Installation Problem I think you'll find you need: ./configure --with-libol=/usr/local/bin for the syslog-ng ./configure, coz that's where libol make install puts /usr/local/bin/libol-config by default. Ted **************************************************************************** ******************** This E-mail message, including any attachments, is intended only for the person or entity to which it is addressed, and may contain confidential information. If you are not the intended recipient, any review, retransmission, disclosure, copying, modification or other use of this E-mail message or attachments is strictly forbidden. If you have received this E-mail message in error, please contact the author and delete the message and any attachments from your computer. You are also advised that the views and opinions expressed in this E-mail message and any attachments are the author's own, and may not reflect the views and opinions of FLEXTECH Television Limited. **************************************************************************** ******************** _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

1 0

RE: [syslog-ng]Syslog-ng Installation Problem
by Rule, Ted 26 Mar '04

26 Mar '04

I think you'll find you need: ./configure --with-libol=/usr/local/bin for the syslog-ng ./configure, coz that's where libol make install puts /usr/local/bin/libol-config by default. Ted ************************************************************************************************ This E-mail message, including any attachments, is intended only for the person or entity to which it is addressed, and may contain confidential information. If you are not the intended recipient, any review, retransmission, disclosure, copying, modification or other use of this E-mail message or attachments is strictly forbidden. If you have received this E-mail message in error, please contact the author and delete the message and any attachments from your computer. You are also advised that the views and opinions expressed in this E-mail message and any attachments are the author's own, and may not reflect the views and opinions of FLEXTECH Television Limited. ************************************************************************************************

1 0

Syslog-ng Installation Problem
by Hagans, John 25 Mar '04

25 Mar '04

To whom it may concern: I am having a problem installing syslog-ng and need some help. I have included installation report files from libol-0.3.9 and syslog-ng-1.6.2. I have attempted the install with various versions of syslog-ng and libol, but I have had no success. I have read the README and INSTALL files for syslog-ng, but they have not provided the assistance I need. Also, I have installed bison and flex. Those two programs installed with no errors. Are there some other dependencies that are not documented? Thanks John T. Hagans North Seattle Community College IT Services Network Supervisor Libol Installation Report ./configure creating cache ./config.cache checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes checking for working aclocal... found checking for working autoconf... found checking for working automake... found checking for working autoheader... found checking for working makeinfo... found checking whether build environment is sane... yes checking for ranlib... ranlib checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking whether make sets ${MAKE}... (cached) yes checking for scsh... no checking for Cygwin environment... no checking for mingw32 environment... no checking how to run the C preprocessor... gcc -E checking host system type... i586-pc-linux-gnu checking build system type... i586-pc-linux-gnu checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependant libraries... pass_all checking for object suffix... o checking for executable suffix... no checking command to parse /usr/bin/nm -B output... ok checking for dlfcn.h... yes checking for ranlib... (cached) ranlib checking for strip... strip checking for objdir... .libs checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.lo... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking dynamic linker characteristics... GNU/Linux ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether -lc should be explicitly linked in... no creating libtool checking for ANSI C header files... yes checking for fcntl.h... yes checking for sys/time.h... yes checking for syslog.h... yes checking for unistd.h... yes checking for poll.h... yes checking for sys/poll.h... yes checking for sys/socket.h... yes checking for working const... yes checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking size of short... 2 checking size of int... 4 checking size of long... 4 checking for socklen_t... yes checking for __attribute__... yes checking for working alloca.h... yes checking for alloca... yes checking for inet_addr in -lxnet... no checking for gethostbyname in -lnsl... yes checking for setsockopt in -lsocket... no checking for select... yes checking for strerror... yes checking for syslog... yes checking for poll... yes updating cache ./config.cache creating ./config.status creating libol.spec creating Makefile creating src/Makefile creating utils/Makefile creating libol-config creating src/olconfig.h Libol Make make Making all in utils make[1]: Entering directory `/apps/syslog-ng/depend/libol/libol-0.3.9/utils' sed -e "s,_SCSH_,," make_class.in >make_class chmod +x make_class make[1]: Leaving directory `/apps/syslog-ng/depend/libol/libol-0.3.9/utils' Making all in src make[1]: Entering directory `/apps/syslog-ng/depend/libol/libol-0.3.9/src' /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c format.c mkdir .libs gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c format.c -fPIC -DPIC -o .libs/format.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c format.c -o format.o >/dev/null 2>&1 mv -f .libs/format.lo format.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c io.c rm -f .libs/io.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c io.c -fPIC -DPIC -o .libs/io.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c io.c -o io.o >/dev/null 2>&1 mv -f .libs/io.lo io.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c werror.c rm -f .libs/werror.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c werror.c -fPIC -DPIC -o .libs/werror.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c werror.c -o werror.o >/dev/null 2>&1 mv -f .libs/werror.lo werror.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c queue.c rm -f .libs/queue.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c queue.c -fPIC -DPIC -o .libs/queue.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c queue.c -o queue.o >/dev/null 2>&1 mv -f .libs/queue.lo queue.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c abstract_io.c rm -f .libs/abstract_io.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c abstract_io.c -fPIC -DPIC -o .libs/abstract_io.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c abstract_io.c -o abstract_io.o >/dev/null 2>&1 mv -f .libs/abstract_io.lo abstract_io.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c gc.c rm -f .libs/gc.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c gc.c -fPIC -DPIC -o .libs/gc.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c gc.c -o gc.o >/dev/null 2>&1 mv -f .libs/gc.lo gc.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c list.c rm -f .libs/list.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c list.c -fPIC -DPIC -o .libs/list.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c list.c -o list.o >/dev/null 2>&1 mv -f .libs/list.lo list.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c read_line.c rm -f .libs/read_line.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c read_line.c -fPIC -DPIC -o .libs/read_line.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c read_line.c -o read_line.o >/dev/null 2>&1 mv -f .libs/read_line.lo read_line.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c xalloc.c rm -f .libs/xalloc.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c xalloc.c -fPIC -DPIC -o .libs/xalloc.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c xalloc.c -o xalloc.o >/dev/null 2>&1 mv -f .libs/xalloc.lo xalloc.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c alist.c rm -f .libs/alist.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c alist.c -fPIC -DPIC -o .libs/alist.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c alist.c -o alist.o >/dev/null 2>&1 mv -f .libs/alist.lo alist.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c stream_buffer.c rm -f .libs/stream_buffer.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c stream_buffer.c -fPIC -DPIC -o .libs/stream_buffer.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c stream_buffer.c -o stream_buffer.o >/dev/null 2>&1 mv -f .libs/stream_buffer.lo stream_buffer.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c pkt_buffer.c rm -f .libs/pkt_buffer.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c pkt_buffer.c -fPIC -DPIC -o .libs/pkt_buffer.lo pkt_buffer.c: In function `do_flush_stream': pkt_buffer.c:108: warning: implicit declaration of function `memcpy' gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c pkt_buffer.c -o pkt_buffer.o >/dev/null 2>&1 mv -f .libs/pkt_buffer.lo pkt_buffer.lo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c resource.c rm -f .libs/resource.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c resource.c -fPIC -DPIC -o .libs/resource.lo gcc -DHAVE_CONFIG_H -I. -I/apps/syslog-ng/depend/libol/libol-0.3.9/src -I. -D_GNU_SOURCE -Wall -O2 -c resource.c -o resource.o >/dev/null 2>&1 mv -f .libs/resource.lo resource.lo /bin/sh ../libtool --mode=link gcc -Wall -O2 -o libol.la -rpath /usr/local/lib format.lo io.lo werror.lo queue.lo abstract_io.lo gc.lo list.lo read_line.lo xalloc.lo alist.lo stream_buffer.lo pkt_buffer.lo resource.lo -lnsl rm -fr .libs/libol.la .libs/libol.* .libs/libol.* gcc -shared format.lo io.lo werror.lo queue.lo abstract_io.lo gc.lo list.lo read_line.lo xalloc.lo alist.lo stream_buffer.lo pkt_buffer.lo resource.lo -lnsl -Wl,-soname -Wl,libol.so.0 -o .libs/libol.so.0.0.0 (cd .libs && rm -f libol.so.0 && ln -s libol.so.0.0.0 libol.so.0) (cd .libs && rm -f libol.so && ln -s libol.so.0.0.0 libol.so) ar cru .libs/libol.a format.o io.o werror.o queue.o abstract_io.o gc.o list.o read_line.o xalloc.o alist.o stream_buffer.o pkt_buffer.o resource.o ranlib .libs/libol.a creating libol.la (cd .libs && rm -f libol.la && ln -s ../libol.la libol.la) make[1]: Leaving directory `/apps/syslog-ng/depend/libol/libol-0.3.9/src' make[1]: Entering directory `/apps/syslog-ng/depend/libol/libol-0.3.9' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `/apps/syslog-ng/depend/libol/libol-0.3.9' Libol Make Install make install Making install in utils make[1]: Entering directory `/apps/syslog-ng/depend/libol/libol-0.3.9/utils' make[2]: Entering directory `/apps/syslog-ng/depend/libol/libol-0.3.9/utils' /bin/sh /apps/syslog-ng/depend/libol/libol-0.3.9/mkinstalldirs /usr/local/bin /usr/bin/install -c make_class /usr/local/bin/make_class make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/apps/syslog-ng/depend/libol/libol-0.3.9/utils' make[1]: Leaving directory `/apps/syslog-ng/depend/libol/libol-0.3.9/utils' Making install in src make[1]: Entering directory `/apps/syslog-ng/depend/libol/libol-0.3.9/src' make[2]: Entering directory `/apps/syslog-ng/depend/libol/libol-0.3.9/src' /bin/sh /apps/syslog-ng/depend/libol/libol-0.3.9/mkinstalldirs /usr/local/lib /bin/sh ../libtool --mode=install /usr/bin/install -c libol.la /usr/local/lib/libol.la /usr/bin/install -c .libs/libol.so.0.0.0 /usr/local/lib/libol.so.0.0.0 (cd /usr/local/lib && rm -f libol.so.0 && ln -s libol.so.0.0.0 libol.so.0) (cd /usr/local/lib && rm -f libol.so && ln -s libol.so.0.0.0 libol.so) /usr/bin/install -c .libs/libol.lai /usr/local/lib/libol.la /usr/bin/install -c .libs/libol.a /usr/local/lib/libol.a ranlib /usr/local/lib/libol.a chmod 644 /usr/local/lib/libol.a PATH="$PATH:/sbin" ldconfig -n /usr/local/lib ---------------------------------------------------------------------- Libraries have been installed in: /usr/local/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,--rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- /bin/sh /apps/syslog-ng/depend/libol/libol-0.3.9/mkinstalldirs /usr/local/include/libol /usr/bin/install -c -m 644 abstract_io.h /usr/local/include/libol/abstract_io.h /usr/bin/install -c -m 644 alist.h /usr/local/include/libol/alist.h /usr/bin/install -c -m 644 format.h /usr/local/include/libol/format.h /usr/bin/install -c -m 644 gc.h /usr/local/include/libol/gc.h /usr/bin/install -c -m 644 io.h /usr/local/include/libol/io.h /usr/bin/install -c -m 644 jpoll.h /usr/local/include/libol/jpoll.h /usr/bin/install -c -m 644 list.h /usr/local/include/libol/list.h /usr/bin/install -c -m 644 objbase.h /usr/local/include/libol/objbase.h /usr/bin/install -c -m 644 objects.h /usr/local/include/libol/objects.h /usr/bin/install -c -m 644 objtypes.h /usr/local/include/libol/objtypes.h /usr/bin/install -c -m 644 pkt_buffer.h /usr/local/include/libol/pkt_buffer.h /usr/bin/install -c -m 644 queue.h /usr/local/include/libol/queue.h /usr/bin/install -c -m 644 read_line.h /usr/local/include/libol/read_line.h /usr/bin/install -c -m 644 resource.h /usr/local/include/libol/resource.h /usr/bin/install -c -m 644 stream_buffer.h /usr/local/include/libol/stream_buffer.h /usr/bin/install -c -m 644 werror.h /usr/local/include/libol/werror.h /usr/bin/install -c -m 644 xalloc.h /usr/local/include/libol/xalloc.h /usr/bin/install -c -m 644 command.h /usr/local/include/libol/command.h /usr/bin/install -c -m 644 io_commands.h /usr/local/include/libol/io_commands.h /usr/bin/install -c -m 644 abstract_io.h.x /usr/local/include/libol/abstract_io.h.x /usr/bin/install -c -m 644 alist.h.x /usr/local/include/libol/alist.h.x /usr/bin/install -c -m 644 io.h.x /usr/local/include/libol/io.h.x /usr/bin/install -c -m 644 list.h.x /usr/local/include/libol/list.h.x /usr/bin/install -c -m 644 read_line.h.x /usr/local/include/libol/read_line.h.x /usr/bin/install -c -m 644 resource.h.x /usr/local/include/libol/resource.h.x /usr/bin/install -c -m 644 io_commands.h.x /usr/local/include/libol/io_commands.h.x /usr/bin/install -c -m 644 command.h.x /usr/local/include/libol/command.h.x /usr/bin/install -c -m 644 queue.h.x /usr/local/include/libol/queue.h.x /usr/bin/install -c -m 644 olconfig.h /usr/local/include/libol/olconfig.h make[2]: Leaving directory `/apps/syslog-ng/depend/libol/libol-0.3.9/src' make[1]: Leaving directory `/apps/syslog-ng/depend/libol/libol-0.3.9/src' make[1]: Entering directory `/apps/syslog-ng/depend/libol/libol-0.3.9' make[2]: Entering directory `/apps/syslog-ng/depend/libol/libol-0.3.9' /bin/sh /apps/syslog-ng/depend/libol/libol-0.3.9/mkinstalldirs /usr/local/bin /usr/bin/install -c libol-config /usr/local/bin/libol-config make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/apps/syslog-ng/depend/libol/libol-0.3.9' make[1]: Leaving directory `/apps/syslog-ng/depend/libol/libol-0.3.9' directory `/apps/syslog-ng/depend/libol/libol-0.3.9' Syslog-ng Installation Report ./configure -with-libol= /apps/syslog-ng/depend/libol/libol-0.3.9 configure: warning: /apps/syslog-ng/depend/libol/libol-0.3.9: invalid host type creating cache ./config.cache checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes checking for working aclocal-1.4... found checking for working autoconf... found checking for working automake-1.4... found checking for working autoheader... found checking for working makeinfo... found checking whether build environment is sane... yes checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for bison... bison -y checking how to run the C preprocessor... gcc -E checking for flex... flex checking for flex... (cached) flex checking for yywrap in -lfl... yes checking lex output file root... lex.yy checking whether yytext is a pointer... yes checking whether make sets ${MAKE}... (cached) yes checking for ANSI C header files... yes checking for malloc.h... yes checking for unistd.h... yes checking for door.h... no checking for stropts.h... yes checking for sys/strlog.h... no checking for stdarg.h... yes checking for sys/klog.h... yes checking for arpa/nameser.h... yes checking for tcpd.h... yes checking for working const... yes checking whether time.h and sys/time.h may both be included... yes checking for modern utmp... yes checking whether to compile klogctl... yes checking size of short... 2 checking size of int... 4 checking size of long... 4 checking for I_CONSLOG... no checking for O_LARGEFILE... yes checking for res_init in <resolv.h>... yes checking for working alloca.h... yes checking for alloca... yes checking for vprintf... yes checking for res_init in -lresolv... no checking for __res_init in -lresolv... yes checking for door_create in -ldoor... no checking for socket in -lsocket... no checking for gethostbyname in -lnsl... yes checking for select... yes checking for snprintf... yes checking for vsnprintf... yes checking for strerror... yes checking for inet_aton... yes checking for strncpy... yes checking for getutent... yes checking for getopt_long... yes checking for strcasecmp... yes checking for strptime... yes checking for TCP wrapper library... -lwrap checking whether to enable Sun STREAMS support... no checking whether to enable Sun door support... no checking whether to enable TCP wrapper support... no checking libol version >= 0.3.13... configure: error: libol-config not found in the specified location Libol-config is in the specied location. #ls -l /apps/syslog-ng/depend/libol/libol-0.3.9/libol-config -rwxr-xr-x 1 root root 1318 Mar 23 17:16 /apps/syslog-ng/depend/libol/libol-0.3.9/libol-config

1 0

RE: [syslog-ng]relay host address changes source hosts ip in mess age
by Hamilton, Andrew 25 Mar '04

25 Mar '04

You need keep_hostname(yes) on both the relay host and the central host. Regards, Drew -----Original Message----- From: William Rude [mailto:wrude@gardrail.com] Sent: Wednesday, March 24, 2004 3:20 PM To: syslog-ng(a)lists.balabit.hu Subject: [syslog-ng]relay host address changes source hosts ip in message Greetings, I've been tasked to setup a syslog relay network from various pops to a centralized syslog server for insert into a database. The problem I'm running into is at the various pops, for example, lets call the first one POP-A. At POP-A, I have syslog-ng version 1.6.0rc4 setup to receive both udp and tcp syslog connections. It in turn, relays the syslog messages to the central server. When I look at the incoming data on the centralized server, the incoming data shows that the source host information is being re-written with the relay hosts ip. System stats are: Solaris 8 intel Syslog-ng 1.6.0rc4 POP-A configuration file follows: options { long_hostnames(off); use_dns(no); use_fqdn(no); dns_cache(no); check_hostname(yes); keep_hostname(no); chain_hostnames(no); # On Solaris, log(3) truncates at 1024 chars log_msg_size(8192); # buffer just a little for performance sync(0); # memory is cheap, buffer messages unable to write (like to loghost) log_fifo_size(10240); # The time to wait before a dead connection is reestablished (seconds) time_reopen(10); create_dirs(yes); owner("root"); group("other"); perm(0600); use_time_recvd(yes); }; source src { # This is the source of syslog. # The default protocal port is 512 udp(); tcp(max-connections(1024)); }; source l_src { # This is the source of syslog. # This is internal messages on the local server internal(); sun-streams("/dev/log"); # This is internal messages on the local server }; destination syslogfile { file( "/var/log/syslogng/$HOST.log" ); udp("1.1.1.1"); }; filter priorityfilter { priority(debug,info,notice,warning,err,crit,alert,emerg); }; ############################################################### log { source(src); source(l_src); filter(priorityfilter); destination(syslogfile); }; ------------------------------------------------------ ------------------------------------------------------ ------------------------------------------------------ Server syslog-ng configuration follows: ------------------------------------------------------ ------------------------------------------------------ ------------------------------------------------------ options { long_hostnames(yes); use_dns(no); use_fqdn(no); dns_cache(no); # dns_cache_size(500); # dns_cache_expire(3600); # dns_cache_expire_failed(3600); # check_hostname(yes); keep_hostname(no); chain_hostnames(no); # On Solaris, log(3) truncates at 1024 chars log_msg_size(8192); # buffer just a little for performance sync(0); # memory is cheap, buffer messages unable to write (like to loghost) log_fifo_size(10240); # The time to wait before a dead connection is reestablished (seconds) time_reopen(10); create_dirs(yes); owner("root"); group("other"); perm(0640); use_time_recvd(yes); }; ############################################################### source src { # This is the source of syslog. # The default protocal port is 512 udp(); # This is internal messages on the local server internal(); }; source l_src { sun-stream("/dev/log" door("/etc/.syslog_door")); internal(); }; destination syslogfile { file( "/var/log/syslogng/$YEAR_$MONTH_$DAY_$HOST.log" ); }; destination program1 { program( /path/to/uber/syslog/program.pl template ("¡$HOST¡$FACILITY¡$PRIORITY¡$LEVEL¡$TAG¡$FULLDATE¡$PROGRAM¡$MSG\n") template-escape(yes) ); }; filter priorityfilter { priority(debug,info,notice,warning,err,crit,alert,emerg); }; filter dropsyslog { not match("syslog-ng*"); }; ############################################################### log { source(src); filter(dropsyslog); filter(priorityfilter); destination(program1); destination(syslogfile); }; ############################################################### log { source(l_src); destination(program1); destination(syslogfile); }; _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

1 0

Logging from a sun or hp unix host to syslog-ng
by Conrad Tiflin (CF) 25 Mar '04

25 Mar '04

Hi Everyone, I have setup a syslog-ng server on sun solaris 9. I now would like to log from a sun solaris box or a hp box on the network. These boxes are setup to send messages to the server. When I do a snoop on port 514 on the syslog-ng server I see that these boxes are sending messages but the server is not storing this info. into a file. The problem must lie with the syslog-ng.conf. I am able to log from cisco pix firewalls without any problem. I assume that the configuration must be Different for logging from hosts then. Does anyone have an idea?, if so what should the configuration be for logging from these boxes. Regards, Conrad ================================================================== This e-mail and its contents are subject to the Telkom SA Limited e-mail legal notice available from mailto:legalnotice@telkom.co.za or http://www.telkom.co.za/TelkomEMailLegalNotice.PDF

2 1

RE: [syslog-ng]relay host address changes source hosts ip in mess age
by "Pedroche, Raúl" 25 Mar '04

25 Mar '04

Greetings, The problem is quite simple: you have set the option "keep_hostname(no)" on both servers, which implies that syslog-ng will not trust the hostname in the packet payload, that is, the hostname by which the original server refers to itself, and will use reverse IP resolution to set it. In this scenario, this means that central server will see packets coming from POP-A and will not use the hostname in the packet but the reverse IP resolution of the packet source IP (or the IP by itself if it can not resolve it). You should remove the option from the central server configuration. Regards, Raúl Pedroche COLT Telecom Email: raul.pedroche(a)colt-telecom.es www.colt.net -----Original Message----- From: Bill [mailto:syslog-ng@gardrail.com] Sent: Wednesday, March 24, 2004 9:28 PM To: syslog-ng(a)lists.balabit.hu Subject: [syslog-ng]relay host address changes source hosts ip in message Greetings, I've been tasked to setup a syslog relay network from various pops to a centralized syslog server for insert into a database. The problem I'm running into is at the various pops, for example, lets call the first one POP-A. At POP-A, I have syslog-ng version 1.6.0rc4 setup to receive both udp and tcp syslog connections. It in turn, relays the syslog messages to the central server. When I look at the incoming data on the centralized server, the incoming data shows that the source host information is being re-written with the relay hosts ip. System stats are: Solaris 8 intel Syslog-ng 1.6.0rc4 POP-A configuration file follows: options { long_hostnames(off); use_dns(no); use_fqdn(no); dns_cache(no); check_hostname(yes); keep_hostname(no); chain_hostnames(no); # On Solaris, log(3) truncates at 1024 chars log_msg_size(8192); # buffer just a little for performance sync(0); # memory is cheap, buffer messages unable to write (like to loghost) log_fifo_size(10240); # The time to wait before a dead connection is reestablished (seconds) time_reopen(10); create_dirs(yes); owner("root"); group("other"); perm(0600); use_time_recvd(yes); }; source src { # This is the source of syslog. # The default protocal port is 512 udp(); tcp(max-connections(1024)); }; source l_src { # This is the source of syslog. # This is internal messages on the local server internal(); sun-streams("/dev/log"); # This is internal messages on the local server }; destination syslogfile { file( "/var/log/syslogng/$HOST.log" ); udp("1.1.1.1"); }; filter priorityfilter { priority(debug,info,notice,warning,err,crit,alert,emerg); }; ############################################################### log { source(src); source(l_src); filter(priorityfilter); destination(syslogfile); }; ------------------------------------------------------ ------------------------------------------------------ ------------------------------------------------------ Server syslog-ng configuration follows: ------------------------------------------------------ ------------------------------------------------------ ------------------------------------------------------ options { long_hostnames(yes); use_dns(no); use_fqdn(no); dns_cache(no); # dns_cache_size(500); # dns_cache_expire(3600); # dns_cache_expire_failed(3600); # check_hostname(yes); keep_hostname(no); chain_hostnames(no); # On Solaris, log(3) truncates at 1024 chars log_msg_size(8192); # buffer just a little for performance sync(0); # memory is cheap, buffer messages unable to write (like to loghost) log_fifo_size(10240); # The time to wait before a dead connection is reestablished (seconds) time_reopen(10); create_dirs(yes); owner("root"); group("other"); perm(0640); use_time_recvd(yes); }; ############################################################### source src { # This is the source of syslog. # The default protocal port is 512 udp(); # This is internal messages on the local server internal(); }; source l_src { sun-stream("/dev/log" door("/etc/.syslog_door")); internal(); }; destination syslogfile { file( "/var/log/syslogng/$YEAR_$MONTH_$DAY_$HOST.log" ); }; destination program1 { program( /path/to/uber/syslog/program.pl template ("¡$HOST¡$FACILITY¡$PRIORITY¡$LEVEL¡$TAG¡$FULLDATE¡$PROGRAM¡$MSG\n") template-escape(yes) ); }; filter priorityfilter { priority(debug,info,notice,warning,err,crit,alert,emerg); }; filter dropsyslog { not match("syslog-ng*"); }; ############################################################### log { source(src); filter(dropsyslog); filter(priorityfilter); destination(program1); destination(syslogfile); }; ############################################################### log { source(l_src); destination(program1); destination(syslogfile); }; _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

1 0

relay host address changes source hosts ip in message
by Bill 24 Mar '04

24 Mar '04

Greetings, I've been tasked to setup a syslog relay network from various pops to a centralized syslog server for insert into a database. The problem I'm running into is at the various pops, for example, lets call the first one POP-A. At POP-A, I have syslog-ng version 1.6.0rc4 setup to receive both udp and tcp syslog connections. It in turn, relays the syslog messages to the central server. When I look at the incoming data on the centralized server, the incoming data shows that the source host information is being re-written with the relay hosts ip. System stats are: Solaris 8 intel Syslog-ng 1.6.0rc4 POP-A configuration file follows: options { long_hostnames(off); use_dns(no); use_fqdn(no); dns_cache(no); check_hostname(yes); keep_hostname(no); chain_hostnames(no); # On Solaris, log(3) truncates at 1024 chars log_msg_size(8192); # buffer just a little for performance sync(0); # memory is cheap, buffer messages unable to write (like to loghost) log_fifo_size(10240); # The time to wait before a dead connection is reestablished (seconds) time_reopen(10); create_dirs(yes); owner("root"); group("other"); perm(0600); use_time_recvd(yes); }; source src { # This is the source of syslog. # The default protocal port is 512 udp(); tcp(max-connections(1024)); }; source l_src { # This is the source of syslog. # This is internal messages on the local server internal(); sun-streams("/dev/log"); # This is internal messages on the local server }; destination syslogfile { file( "/var/log/syslogng/$HOST.log" ); udp("1.1.1.1"); }; filter priorityfilter { priority(debug,info,notice,warning,err,crit,alert,emerg); }; ############################################################### log { source(src); source(l_src); filter(priorityfilter); destination(syslogfile); }; ------------------------------------------------------ ------------------------------------------------------ ------------------------------------------------------ Server syslog-ng configuration follows: ------------------------------------------------------ ------------------------------------------------------ ------------------------------------------------------ options { long_hostnames(yes); use_dns(no); use_fqdn(no); dns_cache(no); # dns_cache_size(500); # dns_cache_expire(3600); # dns_cache_expire_failed(3600); # check_hostname(yes); keep_hostname(no); chain_hostnames(no); # On Solaris, log(3) truncates at 1024 chars log_msg_size(8192); # buffer just a little for performance sync(0); # memory is cheap, buffer messages unable to write (like to loghost) log_fifo_size(10240); # The time to wait before a dead connection is reestablished (seconds) time_reopen(10); create_dirs(yes); owner("root"); group("other"); perm(0640); use_time_recvd(yes); }; ############################################################### source src { # This is the source of syslog. # The default protocal port is 512 udp(); # This is internal messages on the local server internal(); }; source l_src { sun-stream("/dev/log" door("/etc/.syslog_door")); internal(); }; destination syslogfile { file( "/var/log/syslogng/$YEAR_$MONTH_$DAY_$HOST.log" ); }; destination program1 { program( /path/to/uber/syslog/program.pl template ("¡$HOST¡$FACILITY¡$PRIORITY¡$LEVEL¡$TAG¡$FULLDATE¡$PROGRAM¡$MSG\n") template-escape(yes) ); }; filter priorityfilter { priority(debug,info,notice,warning,err,crit,alert,emerg); }; filter dropsyslog { not match("syslog-ng*"); }; ############################################################### log { source(src); filter(dropsyslog); filter(priorityfilter); destination(program1); destination(syslogfile); }; ############################################################### log { source(l_src); destination(program1); destination(syslogfile); };

1 0

relay host address changes source hosts ip in message
by William Rude 24 Mar '04

24 Mar '04

Greetings, I've been tasked to setup a syslog relay network from various pops to a centralized syslog server for insert into a database. The problem I'm running into is at the various pops, for example, lets call the first one POP-A. At POP-A, I have syslog-ng version 1.6.0rc4 setup to receive both udp and tcp syslog connections. It in turn, relays the syslog messages to the central server. When I look at the incoming data on the centralized server, the incoming data shows that the source host information is being re-written with the relay hosts ip. System stats are: Solaris 8 intel Syslog-ng 1.6.0rc4 POP-A configuration file follows: options { long_hostnames(off); use_dns(no); use_fqdn(no); dns_cache(no); check_hostname(yes); keep_hostname(no); chain_hostnames(no); # On Solaris, log(3) truncates at 1024 chars log_msg_size(8192); # buffer just a little for performance sync(0); # memory is cheap, buffer messages unable to write (like to loghost) log_fifo_size(10240); # The time to wait before a dead connection is reestablished (seconds) time_reopen(10); create_dirs(yes); owner("root"); group("other"); perm(0600); use_time_recvd(yes); }; source src { # This is the source of syslog. # The default protocal port is 512 udp(); tcp(max-connections(1024)); }; source l_src { # This is the source of syslog. # This is internal messages on the local server internal(); sun-streams("/dev/log"); # This is internal messages on the local server }; destination syslogfile { file( "/var/log/syslogng/$HOST.log" ); udp("1.1.1.1"); }; filter priorityfilter { priority(debug,info,notice,warning,err,crit,alert,emerg); }; ############################################################### log { source(src); source(l_src); filter(priorityfilter); destination(syslogfile); }; ------------------------------------------------------ ------------------------------------------------------ ------------------------------------------------------ Server syslog-ng configuration follows: ------------------------------------------------------ ------------------------------------------------------ ------------------------------------------------------ options { long_hostnames(yes); use_dns(no); use_fqdn(no); dns_cache(no); # dns_cache_size(500); # dns_cache_expire(3600); # dns_cache_expire_failed(3600); # check_hostname(yes); keep_hostname(no); chain_hostnames(no); # On Solaris, log(3) truncates at 1024 chars log_msg_size(8192); # buffer just a little for performance sync(0); # memory is cheap, buffer messages unable to write (like to loghost) log_fifo_size(10240); # The time to wait before a dead connection is reestablished (seconds) time_reopen(10); create_dirs(yes); owner("root"); group("other"); perm(0640); use_time_recvd(yes); }; ############################################################### source src { # This is the source of syslog. # The default protocal port is 512 udp(); # This is internal messages on the local server internal(); }; source l_src { sun-stream("/dev/log" door("/etc/.syslog_door")); internal(); }; destination syslogfile { file( "/var/log/syslogng/$YEAR_$MONTH_$DAY_$HOST.log" ); }; destination program1 { program( /path/to/uber/syslog/program.pl template ("¡$HOST¡$FACILITY¡$PRIORITY¡$LEVEL¡$TAG¡$FULLDATE¡$PROGRAM¡$MSG\n") template-escape(yes) ); }; filter priorityfilter { priority(debug,info,notice,warning,err,crit,alert,emerg); }; filter dropsyslog { not match("syslog-ng*"); }; ############################################################### log { source(src); filter(dropsyslog); filter(priorityfilter); destination(program1); destination(syslogfile); }; ############################################################### log { source(l_src); destination(program1); destination(syslogfile); };

1 0

Digitailly signed log entries
by Asaf Maruf Ali 24 Mar '04

24 Mar '04

Hello, We are currently setting up a secure logging server for a client using Syslog 1.6.2 and PHP-Syslog 1.4.2 for event management and logging. Needless to say the setup is working very well. The customer further requests that each log entry be digitally signed before being logged. Any ideas on how to do this. I looked through the mailing archives till June 2003 but didn't find any reference. Thank you in advance. Asaf Maruf Ali PING Systems IT Consultants Linux-Networks-Security +9221-5833971

1 0

Integrating Solaris BSM audit with syslog-ng
by Olivia Leonard 23 Mar '04

23 Mar '04

Hi I am trying to set up a unified logging environment for Solaris, HP-UX and Windows NT/2000 servers. The centralized logging and reporting server will run syslog-ng and accept syslog messages (with an agent converter for NT/2000) from all the servers on the network. I will then use swatch to report against these logs, both near real-time for critical events and daily reports for events which must be monitored but are not considered critical. All Solaris boxes will configured to use the Basic Security Module and audit against events such as successful/failed logins, su and so on. Given that the auditd writes it's files in binary and a tool such as praudit must be used to report against them, I was wondering if anyone knew of a way of integrating this into syslog-ng, maybe by using local0 -7, or there is package out there that does this? We live in hope ...... Regards Olivia The Information is this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any other action taken or any views, opinions or advice contained in this email are those of the sending individual and not necessarily those of the firm. It is possible for data transmitted by e-mail to be deliberately or accidentally corrupted or intercepted. For this reason where the communication is by email, J&E Davy does not accept any responsibility for any breach of confidence which may arise from the use of this medium. If you have received this e-mail in error please notify us immediately at mailto:helpdesk@davy.ie and delete this e-mail from your system.

1 0