From owner-freebsd-questions Mon Jun 1 13:30:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26249 for freebsd-questions-outgoing; Mon, 1 Jun 1998 13:30:54 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from jumpgate.cpn.org.au (ppp03.dpac.tas.gov.au [147.109.155.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26174 for ; Mon, 1 Jun 1998 13:30:36 -0700 (PDT) (envelope-from cpn@dpac.tas.gov.au) Received: from jumpgate.cpn.org.au (jumpgate.cpn.org.au [172.16.1.1]) by jumpgate.cpn.org.au (8.8.7/8.8.7) with SMTP id VAA04741 for ; Mon, 1 Jun 1998 21:43:50 +1000 (EST) (envelope-from cpn@dpac.tas.gov.au) Date: Mon, 1 Jun 1998 21:43:50 +1000 (EST) From: Carey Nairn X-Sender: cpn@jumpgate.cpn.org.au To: questions@FreeBSD.ORG Subject: weirdness with 2.2.6 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I am having some strange things happen with my 2.2.6 box. When using su to login as root (whether telnetting in from another machine or logging in at the console), I am getting mysterious hangs with this program. This usually happens after the machine has been up for more than 12 hours. Things to note: - the machine has no keyboard or video card and so diverts all console output to cuaa0. - The terminal I use is not always connected to this machine. - xterm sessions already su'ed to root continue to work - sending a HUP to init doesn't fix the problem - rebooting fixes the problem for at least a few hours - Top reports the state of the the su process as siobi (whatever that means), memory usage is fine (not using any swap), processor is basically idle most of the time. I thought that the problem might be related to there being no terminal on the serial port and getting some sort of a blocking I/O situation when trying to write the su message to the console, but if that was the case I should have the problem EVERY time I try to su (even straight after a reboot). The machine is a 486-66 with 16MB RAM Any thoughts/ideas about this would be most welcome. cheers, Carey Nairn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message