From owner-freebsd-questions Tue Feb 6 18:16:30 2001 Delivered-To: freebsd-questions@freebsd.org Received: from w2xo.pgh.pa.us (ipl-229-034.npt-sdsl.stargate.net [208.223.229.34]) by hub.freebsd.org (Postfix) with ESMTP id 7E95037B401 for ; Tue, 6 Feb 2001 18:16:12 -0800 (PST) Received: from shazam (shazam [192.168.5.3]) by w2xo.pgh.pa.us (8.9.3/8.9.3) with ESMTP id CAA11200; Wed, 7 Feb 2001 02:16:04 GMT (envelope-from durham@w2xo.pgh.pa.us) Date: Tue, 6 Feb 2001 21:16:37 -0500 (EST) From: Jim Durham X-Sender: durham@shazam.int To: "J. Seth Henry" Cc: questions@FreeBSD.ORG Subject: Re: questions-digest V5 #85 In-Reply-To: <006901c0905a$5fc66db0$0e01a8c0@guinevere> 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 On Tue, 6 Feb 2001, J. Seth Henry wrote: > Given the description of the problem, I would say that the problem is in X. > Every great once in a while, my X session will lock - producing similar > symptoms: no keyboard/mouse. The system is far from dead though. I have a > dumb terminal attached to one of the serial ports, and I can log in as root > and kill the offending processes. Then, I kill -HUP init, and this *usually* > restores the console. Keep in mind, it's only happened about 3 or 4 times - > and it worked twice... ;) If that doesn't work, I can gracefully shutdown > the system. Definitely recommended! > > > Since you said you could ping the machine, which implies you have more than > one on your network. You should be able to telnet/ssh in and do the same. > Nope, I mentioned that you can't telnet or ftp in. I haven't tried a serial terminal. I could do that. Thanks, Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message