From owner-freebsd-questions  Fri Sep  6 12:35:57 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA21857
          for questions-outgoing; Fri, 6 Sep 1996 12:35:57 -0700 (PDT)
Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA21847
          for <questions@freebsd.org>; Fri, 6 Sep 1996 12:35:53 -0700 (PDT)
Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.7.1/8.7.1) with SMTP id PAA08932; Fri, 6 Sep 1996 15:35:50 -0400 (EDT)
Received: from jandrese.async.vt.edu (jandrese.async.vt.edu [128.173.20.208]) by sable.cc.vt.edu (8.6.12/8.6.12) with SMTP id PAA27477; Fri, 6 Sep 1996 15:35:48 -0400
Date: Fri, 6 Sep 1996 15:39:27 +0000 ()
From: Nessus <jandrese@vt.edu>
X-Sender: jandrese@jandrese.async.vt.edu
To: "Sean J. Schluntz" <schluntz@gromit.pinpt.com>
cc: questions@freebsd.org
Subject: Re: XF86 & fvwm Problem, Help?
In-Reply-To: <2.2.32.19960906185858.00862674@wallace.pinpt.com>
Message-ID: <Pine.BSF.3.91.960906153428.528B-100000@jandrese.async.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 6 Sep 1996, Sean J. Schluntz wrote:

> Hello, I have XF86_S3 and fvwm running very well with one strange problem.
> Every time it starts and the login and xterm windows open, and every time I
> open another shell I get the follwing error:
> 
> Fatal server error:
> Server is already active for display 0
>         If this server is no longer runing, remove /tmp/.X0-lock
>         and start again.
> 
> Then after a delay (30-50 seconds) I get the normal prompt.
> 
> This happens even after the system has been restarted and no other
> X-Sessions have been started.  The file .X0-lock does not appear when X is
> not running and only appears after I login and start X.  What can I do?
> 
the .X0-lock file is a flag file that XWindows uses to keep from being 
started twice.  What you have probabally done is put startx in your shell 
initalization file (.cshrc for csh, .zshrc for zsh, etc...  Read the 
manpage for your shell).  When you start your Xterms, they execute that 
script and try to start X again.  What you need is to check to see if the 
.X0-lock file exists, and if it doesn't, then run startx; or run startx 
manually from the command line.  

:::::::::::::::::::::::::::. .   .   .   .   ..::::::::::::::::::::::::::::
::     Jason Andresen      :. . . . . . . . . :               Nessus     ::
::     jandrese@vt.edu     :.:.:.:.:.:.:.:.:.::        nessus@vt.edu     ::
 :.........................: Quote of the day :..........................:
If you keep an open mind people will throw a lot of garbage in it.
:::::::::::.:.:.:.:.:.:.:.........................:.:.:.:.:.:.:.:::::::::::