From owner-freebsd-current Wed Apr 22 09:31:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16094 for freebsd-current-outgoing; Wed, 22 Apr 1998 09:31:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16059 for ; Wed, 22 Apr 1998 16:31:05 GMT (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.8/8.8.7) with SMTP id LAA16637; Wed, 22 Apr 1998 11:29:38 -0500 (EST) Date: Wed, 22 Apr 1998 11:29:38 -0500 (EST) From: John Fieber To: Mike Smith cc: "Jordan K. Hubbard" , Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= , Kazutaka YOKOTA , "Alok K. Dhir" , current@FreeBSD.ORG Subject: Re: Disappearing keyboard In-Reply-To: <199804221612.JAA00593@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Apr 1998, Mike Smith wrote: > > > This is evil and should never have been suggested in the docs. > > > > Why? It's always worked just great for me and I've had it like > > this for over 3 years. > > "Because if your X server crashes it just loops forever" > > At least that's the pathetic excuse that I've heard most often. And not even correct. If *xdm* immediately crashes, it will loop a couple times but then init notices something is amiss and stops trying to start it. If your *X server* crashes, xdm restarts it. Whether you started xdm int /etc/ttys or by some other mechanism has nothing to do with it with this behavior. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message