Age | Commit message (Collapse) | Author |
|
|
|
lines as the end of a stock syslog.conf you're going to spend some time
figuring why is not working as it should; problem found by
riq@core-sdi.com, millert@ ok.
|
|
|
|
select case
|
|
some conversations with alejo@core-sdi.com, not sure yet if this is 100%
perfect, but i have tested it and it works..
|
|
(poorly) by hand. Also fixes a potential one byte overflow noted
by Solar Designer.
|
|
|
|
|
|
cleanup along the way.
|
|
least, this is the impression I get from looking at a lot of Perl docs.
|
|
|
|
wait3 -> waitpid (for portability)
|
|
|
|
is used instead; kwesterback@home.com
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
syslogd should create & listen to. As in "syslogd -a /chroot/dev/log",
I'm sure you get the idea.
|
|
change SIGHUP handler to only set a flag that the main loop catches. But
I'm lazy, and starting to believe noone gives a damn...
|
|
|
|
Suggested by: Theo
|
|
|
|
|
|
Current syslog.conf files are still understood andtreated the same.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
joerg
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Doesn't look to be exploitable.
|
|
|
|
|
|
retain openbsd changes too.
|