From owner-freebsd-stable Sun Dec 30 8:35:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bastion.internal.lustygrapes.net (dhcp065-024-083-096.columbus.rr.com [65.24.83.96]) by hub.freebsd.org (Postfix) with ESMTP id AA3BC37B416 for ; Sun, 30 Dec 2001 08:35:42 -0800 (PST) Received: from nivomede.internal.lustygrapes.net (nivomede.internal.lustygrapes.net [192.168.10.65]) by bastion.internal.lustygrapes.net (Postfix) with ESMTP id 5BC0F5A3E; Sun, 30 Dec 2001 11:35:41 -0500 (EST) Date: Sun, 30 Dec 2001 11:35:41 -0500 (EST) From: Brian McDonald X-X-Sender: To: David Malone Cc: Chris Johnson , Subject: Re: syslogd blocking => can't su to root In-Reply-To: <200112301340.aa84281@salmon.maths.tcd.ie> Message-ID: <20011230113124.O2732-100000@nivomede.internal.lustygrapes.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 30 Dec 2001, David Malone wrote: > Date: Sun, 30 Dec 2001 13:40:12 +0000 > From: David Malone > To: Chris Johnson > Cc: stable@FreeBSD.ORG > Subject: Re: syslogd blocking => can't su to root [snip] > I can't think of an easy way to fix the problem - killing and > restarting syslogd might fix it, but there is a possibility the > console will still block when syslogd is restarted... As mentioned in another post, I've seen these problems as well. After I killed and restarted syslogd, some ttys were indeed locked up: root 61092 0.0 0.4 924 536 v3- IEs+ 21Apr01 0:00.00 /usr/libexec/getty Pc ttyv3 root 53250 0.0 0.4 924 540 v1- IEs+ 14Jul01 0:00.01 /usr/libexec/getty Pc ttyv1 Brian -- Brian McDonald, MCP Klein bottle for sale. Inquire within. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message