src/lib/libc/gen/syslog.c, branch release/2.2.5_cvs

This commit was manufactured by cvs2svn to create tag

1997-10-21T01:56:05+00:00

'RELENG_2_2_5_RELEASE'.

This commit was manufactured to restore the state of the 2.2.5-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

YAMFC: rev 1.13 of both files, providing backward binary compatibility

1997-03-23T19:09:07+00:00

if /var/run/log could not be found.

General -Wall warning cleanup, part I.

1996-07-12T18:57:58+00:00

Submitted-By: Kent Vander Velden

If the send() to the AF_UNIX socket to the syslogd fails, attempt to

1996-03-02T19:56:16+00:00

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..

Minor cleanup, mostly unused vars and missing #includes.

1995-10-22T14:37:11+00:00

Add $Id$ since this version of the file has diverged from the BSD base a

1995-10-21T07:05:01+00:00

fair bit.  I forgot to add it when I made the fixes some time ago.

Fix the problem that I aroused with the last commit..

1995-10-05T00:11:15+00:00

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.

Fix security bugs with a "new approach", using stdio's powerful buffer

1995-09-15T13:53:39+00:00

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.

National date/time representation in syslog logfiles looks ugly,

1995-08-29T13:21:53+00:00

change strftime to ctime. Logfiles must have default (english) date/time
representation for access/view from various places.

Fix bracket error for LogMask

1995-05-02T17:46:30+00:00

Submitted by: Ruslan Belkin