From owner-freebsd-smp Thu Jul 22 21:21:13 1999 Delivered-To: freebsd-smp@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id D52E614C0B for ; Thu, 22 Jul 1999 21:21:02 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1003) id BD0E0F818; Fri, 23 Jul 1999 00:17:44 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id B0B999B15; Fri, 23 Jul 1999 00:17:44 -0400 (EDT) Date: Fri, 23 Jul 1999 00:17:44 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Kazutaka YOKOTA Cc: freebsd-smp@freebsd.org Subject: Re: SMP + XDM = keyboard lockup In-Reply-To: <199907230402.NAA02136@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 23 Jul 1999, Kazutaka YOKOTA wrote: > >I believe that if what you are saying is correct, merely following > >the xdm documentation and starting the X server in /etc/ttys should > >resolve his problem. > > I guess it may not. After init forks and execs getty and xdm, we > don't know the exact order in which these processes will be scheduled > to run on which CPU, do we? /etc/ttys does not ensure the order of > execution. > > If xdm happens to run before other getty processes, it may grab a vty > which will be eventually opened by a getty later. > vty's are assigned in /etc/ttys, though: ttyv4 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure ^^^^^ so it the starting order shouldn't matter, unless you have a getty and xdm assigned the same vty, and then it _should_ lock up whether using SMP or not. ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message