Date: Sun, 17 Feb 2002 17:59:19 +0000 From: David Malone <dwmalone@maths.tcd.ie> To: "Todd C. Miller" <Todd.Miller@courtesan.com> Cc: audit@FreeBSD.ORG, Chris Johnson <cjohnson@palomine.net>, Brian McDonald <brian@lustygrapes.net> Subject: Re: Syslog hangong on console. Message-ID: <200202171759.aa61427@salmon.maths.tcd.ie> In-Reply-To: Your message of "Sun, 17 Feb 2002 10:43:09 MST." <200202171743.g1HHhATG025320@xerxes.courtesan.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Below is the diff I committed to OpenBSD some time ago. It goes a > bit farther and opens all files with O_NONBLOCK and then changes > to blocking writes for real files. Looks potentially useful - I'll see if I can drag it into our syslogd. I dunno if you want to consider the patch I posted for OpenBSD, as it could be useful if syslogd becomes unresponsive for some other reason and the console is blocking. BTW - some people seemed to be indicating that syslogd was blocking at some stage other than the open, which is what I wasn't able to reproduce. FreeBSD's syslogd uses ttymsg() to write to the tty, which should never block. The only way I could see it happening was if isatty() lied after the tty was opened. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi? <200202171759.aa61427>