Hello, What environment do you people use for building and running syslog-ng? I use gcc 2.7.2.3 and linux 2.0.29 libc5 system and have only segfaults when try to run this program. Has it got any requirements concerning the system libraries? --- Arek J.
What environment do you people use for building and running syslog-ng? I use gcc 2.7.2.3 and linux 2.0.29 libc5 system and have only segfaults when try to run this program. Has it got any requirements concerning the system libraries?
hmm... the only thing that may be missing is poll(), but if you compiled it, it should be working. Which version of syslog-ng were you trying? -- Bazsi PGP key: http://www.balabit.hu/pgpkey.txt, or finger bazsi@balabit.hu
On Mon, 10 May 1999, Balazs Scheidler wrote:
What environment do you people use for building and running syslog-ng? I use gcc 2.7.2.3 and linux 2.0.29 libc5 system and have only segfaults when try to run this program. Has it got any requirements concerning the system libraries?
hmm... the only thing that may be missing is poll(), but if you compiled it, it should be working. Which version of syslog-ng were you trying?
Your latest 1.1.14 and the problem seems to be in the main_loop function. It gets segfault when executes io_iter function. I run the program with -d parameter, so it should print some debug info. When I run without any parameters it just quits in go_background function after executing pause statement. Strange things... --- Arek J.
What environment do you people use for building and running syslog-ng? I use gcc 2.7.2.3 and linux 2.0.29 libc5 system and have only segfaults when try to run this program. Has it got any requirements concerning the system libraries?
hmm... the only thing that may be missing is poll(), but if you compiled it, it should be working. Which version of syslog-ng were you trying?
Your latest 1.1.14 and the problem seems to be in the main_loop function. It gets segfault when executes io_iter function. I run the program with -d parameter, so it should print some debug info. When I run without any parameters it just quits in go_background function after executing pause statement. Strange things...
by default syslog-ng goes into the background by fork()-ing and killing the parent via a SIGTERM, so that all initializations are performed by the time the parent exists. -- Bazsi PGP key: http://www.balabit.hu/pgpkey.txt, or finger bazsi@balabit.hu
participants (2)
-
Arek Jankowski
-
Balazs Scheidler