I usually find that one side of the socket is being kept open... Make sure the server's not running (or stalled) in background somewhere... and make sure the client isn't hidden in nirvana either!
Just a minute... (Wishing you where here, Chicago is playing...) okay back... Where was I? I suspect the client check for him extra carefully... On Wed, 2002-12-11 at 18:37, [EMAIL PROTECTED] wrote: > I'd assumed that there weren't any operating systems vulverable to "dead > socket"s, but that sure sounds like what you've got. A socket isn't > closed properly when a program exits, and the IP stack doesn't make it > available. Only cure - reboot (or stop/restart stack, on really old > systems with add-on IP stacks). > > Tim Conway > [EMAIL PROTECTED] reorder name and reverse domain > 303.682.4917 office, 303.921.0301 cell > Philips Semiconductor - Longmont TC > 1880 Industrial Circle, Suite D > Longmont, CO 80501 > Available via SameTime Connect within Philips, caesupport2 on AIM > "There are some who call me.... Tim?" > > > > > > > > > > Mike Miller <[EMAIL PROTECTED]> > Sent by: > [EMAIL PROTECTED] > 12/04/02 12:49 PM > > > To: David Howe <[EMAIL PROTECTED]> > cc: [EMAIL PROTECTED] > (bcc: Tim Conway/LMT/SC/PHILIPS) > Subject: RE: "A VNC server is already running as :10", but it isn't! > Classification: > > > > On Wed, 4 Dec 2002, David Howe wrote: > > > Possibly the .pid file (that vncserver checks to see if a instance is > > already running) is still in the user's ~/.vnc? > > > No. It's perplexing. There is no sign of a pid file and vncserver -kill > :10 won't work because it can't find the pid! I don't know why Xvnc > thinks something is running on :10. > > Some of you made the helpful suggestion that /tmp/.X11-unix/ is causing > the problem. Maybe so, but I don't see evidence of that. The same user > was able to run :11 and create the X11 lock file in the /tmp/.X11-unix/ > directory. There is no X10 file in that directory. > > Subsequently, I have gotten users running :12, :13, :14, and all of them > have the same group/user permissions as the user who couldn't run on :10. > It was only 10 that had a problem, not 9, 11, etc.!! Strange. > > Mike > > -- > Michael B. Miller, Ph.D. > Assistant Professor > Division of Epidemiology > University of Minnesota > http://taxa.epi.umn.edu/~mbmiller/ > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
