April 1999 - syslog-ng - lists.balabit.hu

portability fixes
by Balazs Scheidler 28 Apr '99

28 Apr '99

Hello, I have released syslog-ng 1.1.10, and libol 0.1.8 fixes a couple of bugs compiling it on Solaris (tested on "SunOS almos 5.6 Generic sun4d sparc SUNW,SPARCcenter-2000") and should also fix that BSD header problem. (though this is not tested yet) Nothing else changed now. -- Bazsi PGP key: http://www.balabit.hu/pgpkey.txt, or finger bazsi(a)balabit.hu

1 0

syslog-ng 1.1.9
by Balazs Scheidler 28 Apr '99

28 Apr '99

I have released syslog-ng version 1.1.9, the latest development version of syslog-ng. I have added parameter parsing, the ability to go into the background and several bugfixes. You'll need libol 0.1.7, so be sure to download that one too. This version is something that could also be used in production environment. libol has been completely split off, and it is installed as a shared library on your system. I have removed the --with-libol switch from configure, syslog-ng will automatically find your installed version of libol. (using the installed libol-config script) I think I'll do a feature freeze now, stabilize syslog-ng, and release 1.2.x as it is, since advanced features are not important for everyone. So please tell me any build and runtime problems you encounter. -- Bazsi PGP key: http://www.balabit.hu/pgpkey.txt, or finger bazsi(a)balabit.hu

2 4

Re: syslog-ng -- confirmation of subscription -- request 502636
by Stefan Monnier 28 Apr '99

28 Apr '99

confirm 502636

1 0

Re: syslog-ng -- confirmation of subscription -- request 502634
by Stefan Monnier 28 Apr '99

28 Apr '99

confirm 502634

1 0

Re: syslog-ng -- confirmation of subscription -- request 502636
by Stefan Monnier 28 Apr '99

28 Apr '99

confirm 502636

1 0

Re: syslog-ng -- confirmation of subscription -- request 502636
by Stefan Monnier 27 Apr '99

27 Apr '99

confirm 502636

1 0

Re: [syslog-ng] syslog-ng 1.1.7 released
by Stefan Monnier 27 Apr '99

27 Apr '99

Richi Plana said: > One problem Un*x systems administrator haven't totally agreed on is > how to rotate the logs if there was no way to reset the daemon which > had opened the log (and kept it open). The problem has to do with I have never had such a problem and any such program should just be fixed (or not be used). > filehandles. Some programs open a log and keep it open instead of > closing and reopening them when the need arises. Some admins say log > rotators should just cp the log to a backup and do the equivalent of a > 'cat /dev/null > logfile'. (which may cause some problems in some > situations). You'll end up creating big sparse files, which is OK except that `cp' will most likely not keep the sparseness so the backups will be big mostly empty (but not sparse) files. > Personally, I believe there to be three solutions to log rotation: 1) > If the program doesn't support log rotation, kill the daemon, rotate > the logs and restart the program; 2) if the program only supports > SIGHUP to re-read the configs and close and reopen the logs, just cp > the file and SIGHUP it; and, 3) (the best solution) if the program > supports a way to close, mv and reopen a new log file, then all your > problems are solved. If you don't like the name the program used for > the backup, just mv it. Solution 2 is bogus because it suffers from a race condition. You really don't want to use `cp' but `mv' there: mv log log.bak touch log; chmod 640 log kill -HUP <daemon> Solution 3 is only acceptable if the destination of the `mv' is known so that you can easily do postprocessing of this backed up log file. I'm thoroughly against any logrotation support in any program, except for the usual reopen-upon-sighup. The few programs that support it never support a wide enough range of alternatives. Log rotation is better served by separate tools. Of course, as long as you can turn off the logrotation (and use the conventional mv+sighup method), it's only a question of wasted resources (human resources for coding, mostly) and an additional source of bugs. Stefan

2 1

central log host
by Valur Guðmundsson 26 Apr '99

26 Apr '99

Is it posible to set up a central log host that takes log messages from many machines through the same port and then sorts the messages depending on name of the host that sent it.

2 1

Where are some docs?
by Marcin Okraszewski 25 Apr '99

25 Apr '99

Can anyone tell me, where can I find documents that describe config file. There wasn't any doc directory in the archive (1.1.8), and in README was written that there should be. -- -------------------------------------------------------------------- Marcin Okraszewski mailto:okrasz@vlo.ids.gda.pl http://www.vlo.ids.gda.pl/~okrasz/ --------------------------------------------------------------------

3 2

syslog-ng 1.1.8 and libol 0.1.6
by Balazs Scheidler 20 Apr '99

20 Apr '99

Hi, I have released syslog-ng 1.1.8 and the corresponding libol version 0.1.6. This version adds support for udp, tcp and unix destinations. (1.1.7 only supported them as sources) Error recovery is not there yet, so if a given destination is not running, it will cause problems for syslog-ng. libol 0.1.6 fixes a few bugs, and I added a libol-config script (similar to gtk-config in gtk) I hope this eliminates build problems some of you encountered on Solaris. -- Bazsi PGP key: http://www.balabit.hu/pgpkey.txt, or finger bazsi(a)balabit.hu

1 0