| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Submitted-By: Kent Vander Velden <graphix@iastate.edu>
|
| |
|
|
|
|
|
|
| |
reconnect once using the saved openlog() parameters.
This helps one of the system startup race conditions. If syslogd takes too
long to get going, some daemons can fail the connection and forever log
to the console even though the syslogd is running. That is ..unfortunate..
|
| | |
|
| |
|
|
| |
fair bit. I forgot to add it when I made the fixes some time ago.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
What was happening, is if syslogd was not running, syslog() would do
a strcat("\r\n") on a non-null-terminated buffer, and write it to the console.
This meant that sometimes extra characters could be written to the console
during boot, depending on the stack contents.
This totally avoids the potential problem by using writev() like the rest
of the does, and avoid modifying the buffer after the trouble we've gone to
to carefully protect it.
This is actually a trivial fix, in spite of the long commit message.. :-)
It only appeared during boot and shutdown with syslogd stopped.
|
| |
|
|
|
|
|
|
| |
control hooks.
It is similar to an unrolled multi-part snprintf(), in that a "FILE *" is
attached to a string buffer. There is also an optimisation for the case
where the syslog format string does not contain %m, which should improve
performance of "informational" logging, like from ftpd.
|
| |
|
|
|
| |
change strftime to ctime. Logfiles must have default (english) date/time
representation for access/view from various places.
|
| |
|
|
| |
Submitted by: Ruslan Belkin <rus@home2.UA.net>
|
| |
|
