Re: startxwin.exe no longer exists?

[mathog <mathog@caltech.edu>]

On 16-Dec-2014 15:39, Erik Soderquist wrote:
> My best guess (and this is only a guess) is that
> something is causing X to crash as it shuts down on your system,
> causing the lock files to be left behind.

There is no reason that should happen unless the startxwin script also 
crashes - and that basically should never happen.  The script should 
clean up any mess that the binary might leave, and it should handle all 
conditions that might result from some process it has started crashing.  
That is, in the script (pseudocode):

# If there is an existing lock file:
#   Test is there also an existing X11 binary process?
#     yes - abort with message: X11 server already running
#     no  - remove lock file
##########
# do whatever housekeeping is needed
#   then start binary
/path/X11_server_binary $args
#no matter how binary exits...
rm /path/.X*lock

The only time a script might not have a chance to run the last command 
is if it starts the server via "nohup binary &", assuming such a thing 
is even possible in cygwin, and then exits without waiting around for 
the binary to exit.  Or, of course, if the whole system crashes, but 
that isn't the issue the end users are having.

Regards,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/