From owner-freebsd-audit Sun Feb 17 9:59:23 2002 Delivered-To: freebsd-audit@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id F2A0A37B400 for ; Sun, 17 Feb 2002 09:59:19 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 17 Feb 2002 17:59:19 +0000 (GMT) To: "Todd C. Miller" Cc: audit@FreeBSD.ORG, Chris Johnson , Brian McDonald Subject: Re: Syslog hangong on console. In-reply-to: Your message of "Sun, 17 Feb 2002 10:43:09 MST." <200202171743.g1HHhATG025320@xerxes.courtesan.com> X-Request-Do: Date: Sun, 17 Feb 2002 17:59:19 +0000 From: David Malone Message-ID: <200202171759.aa61427@salmon.maths.tcd.ie> Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > 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