Hi, I've released syslog-ng 1.4.1. This time I announce it to this list only, and if no bugs show up in two-three days, the announcement goes up to freshmeat. I've fixed a couple of bugs in this release: * fixed a filter evaluation bug (not in 'or' and 'and') * configuration file reading with syntax errors * pipe() cleanup This driver readds the requirement for GNU flex. I need a way to reinitialize lex buffers, and I know how to do that only with GNU flex (yyreinit(), patches to support other lex versions are welcome) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
Hi list! I have a strange fenomen to report: Sometimes when doing "kill -1" on a client that is sending logs with tcp to a server, the _server_ dies silently. Truss gives a *big* burst of output on the server (about 300 lines of time() calls), it looks like all the hardware devices (keyboard, mouse, stdin, disks, nw-cards) outputs a line into kern at the same time. I cannot reproduce the death on low-volume machines, only on our prime syslog server (100 hosts, about 5 messages/second) dies sometimes when a client with syslog-ng (with tcp enabled) does a "kill -1". Have anyone experienced anything like this? syslog-ng 1.4 CLIENT: SunOS unna4 5.6 Generic_105181-19 sun4u sparc SUNW,Ultra-2 options { long_hostnames(off); sync(0); use_fqdn(yes);}; destination loghost { tcp("hostname.domain.tld" port(514)); }; log {.... destination(loghost); }; SERVER: SunOS syslog 5.7 Generic_106541-09 sun4m sparc SUNW,SPARCstation-20 options { long_hostnames(off); sync(0); use_fqdn(yes); use_dns(yes);}; source tcplog { tcp(ip(0.0.0.0) port(514)); }; destination tcpauto { file("/var/log/tcp/$HOST.$FACILITY"); }; log { source(tcplog); destination(tcpauto); }; /Joakim
Hi, I'm trying to use syslog-ng to read from hp-ux native fifo-file /dev/log The program seems to work fine, but i'm getting a lot of strange lines in my destination-files. Maybe hp-ux is logging some extra info to /dev/log. To test if that is the case, I kill'ed my original syslogd and did a "cp /dev/log output-file" and in another shell I executed "logger hejsa" size of output-file is 2048 Bytes. Is this the right way to get that kind of information? Anyway - I think the content of the file is strange !? A hex-dump of the file is attached to this mail (hope it's ok to do this). -Klaus -- Klaus Groenhoej Kommunedata A/S Hadsundvej 184 9100 Aalborg Denmark Phone: (+45)44601000 #2677 Direct: (+45)44602677 Fax: (+45)44602990
participants (3)
-
Balazs Scheidler
-
Joakim Rastberg
-
Klaus Groenhoej