This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

PR libc/1665: syslog() blocks

To: libc-hacker at sourceware dot cygnus dot com
Subject: PR libc/1665: syslog() blocks
From: Mark Kettenis <kettenis at wins dot uva dot nl>
Date: Tue, 1 Aug 2000 00:33:03 +0200

I've verified that syslog() indeed blocks when I use a `fake' syslogd
(i.e. a program that binds a socket to /dev/log, but then just sleeps
and doesn't read it).  However simply using non-blocked mode isn't an
option, since it would mean that under high load messages could be
lost.  And, as Ulrich already indicated, a malicious user could
prevent logging important events by writting huge amounts of data to
/dev/log.  AFAICT all the BSD's still use code similar to ours.
IMHO people should use a bug-free syslogd.

OK to close the bug report?

Mark

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]