This is the mail archive of the
mailing list for the glibc project.
Re: Does syslog have an internal buffer?
- From: Petter Reinholdtsen <pere at hungry dot com>
- To: Dan Tihelka <dtihelka at kky dot zcu dot cz>
- Cc: libc-alpha at sources dot redhat dot com
- Date: Sun, 15 Aug 2004 15:44:37 +0200
- Subject: Re: Does syslog have an internal buffer?
- References: <411B62E0.email@example.com>
- Reply-by: Tue, 1 Jan 1801 04:37:40 +1000
> I would like to ask you, if a syslog (in glibc library) has an
> internal buffer for a case that syslogd is not running. What does
> glibc, if it can not connect syslogd? (I found somewhere that the
> message is printed to console, but in my case it means that it is lost
> forever :-(( ).
There is no internal buffer in glibc for syslog messages. It would
not make sense, as the programs syslogging might terminate before the
syslogd is available to receive any messages.
> What do you thing about an idea that syslog in glibc has a internal
> circular buffer of several kB of size; whenever the connection to
> syslogd was not successful the message would be stored into the
> buffer. If the connection is successful, whole buffer would be send to
> Moreover it might be useful when syslogd crashes (although I do not
> suppose it :-)) or is restarted.
Interesting idea, but I'm not sure how useful it would be. I
recommend starting syslogd sooner in the boot process instead.