Re: vncserver: cannot restart on same display

[Erik Steffl <steffl@bigfoot.com>]

Jaye Inabnit ke6sls wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Friday 11 October 2002 06:36 pm, Erik Steffl wrote:
> >   how come it is not possible to run vncserver reusing the display
> > number? the following should work:
> >
> >   vncserver :1
> >   vncserver -kill :1
> >   vncserver :1
> >
> >   the first two work, the third one does not, her's the error mesage
> > from vncserver (which is a perl wrapper):
> >
> > billteam:~> vncserver :2
> > ELVIS: cannot bind to 6000 + 2 [Address already in use]
> > A VNC server is already running as :2
> > billteam:~>
> >
> >   (I added the ELVIS message)
> >
> >   Xvnc complains about existing lock file (even though Xvnc that was
> > running on given display is gone). here's the message from Xvnc when I
> > manually remove /tmp/.X1-lock:
> >
> > billteam:~> Xvnc :1
> > _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
> > _XSERVTransMakeAllCOTSServerListeners: server already running
> >
> > Fatal server error:
> > Cannot establish any listening sockets - Make sure an X server isn't
> > already running
> >
> >   lsof | greo 6001 doesn't show anything. I verified that vnc is not
> > running after vncserver -kill
> >
> >   the probem seems to exist only for :1, I can kill vnc on :2 and then
> > start Xvnc :2 again (but not vncserver).
> >
> >   I have seen this problem on two machines (so far).
> >
> >   any ideas on what's going on?
> >
> >       erik
> 
> Greetings Erik:
> 
> "man vncserver" will help understand a little better.  The server adds a log
> entry (lock file) that remains even if you kill the server.  There is an
> option to both kill vnc *and* remove the lock on a given display in a single
> command.  You can manually remove it too.  Look in ~/.vnc in the home
> directory where you started the server.  You could probably do a bash script
> to do this too, but I just the kill and clean options when I kill the server.

  that's definitely not it. as far as I know it is only relevant to
vncserver (perl wrapper), not Xvnc and the server:1.pid is not there
anyway (not even server:1.log hich shouldn't matter at all).

	erik