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
snip
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
On 17-Dec-2014 09:40, Erik Soderquist wrote:
snip
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
snip
So you want your script to completely mask and/or destroy any evidence
that something crashed??
No, that is the log file, this is the lock file. It should rotate the log
file from the previous run and delete the lock file.
How often do you check your log files for crashes when you
On 17-Dec-2014 10:35, Erik Soderquist wrote:
How often do you check your log files for crashes when you have your
script hiding the fact that it crashed from you?
Fine, have the script emit a warning when this situation is encountered.
Personally I have never seen the X11 server crash
startxwin.exe no longer
exists. Somehow I missed where this was removed, so what is the
recommended way of starting X from a desktop icon now?
I seem to recall that startxwin.exe was introduced some time ago
because using a script to start X was inadequate somehow, but I don't
remember
On 12/16/2014 8:00 AM, Erik Soderquist wrote:
snip
Sure, display :0 is unavailable; checking DISPLAY in the (unwanted)
xterm shows DISPLAY is set to :5. Why's that I wonder?
Further investigation shows ls -ltr /tmp:
-r--r--r-- 1 william None 11 Nov 28 17:43 /tmp/.X0-lock
-r--r--r-- 1
snip
Shouldn't the startxwin script check for running instances and delete all
lock-files related to non-existent instances? Why must this be a manual
operation?
I generally recommend against automagic cleanup of lock files from
dead sessions being a general default because that also wipes
On 12/16/2014 9:06 AM, Erik Soderquist wrote:
snip
Shouldn't the startxwin script check for running instances and delete all
lock-files related to non-existent instances? Why must this be a manual
operation?
I generally recommend against automagic cleanup of lock files from
dead sessions
Erik Soderquist wrote:
snip
Shouldn't the startxwin script check for running instances and delete all
lock-files related to non-existent instances? Why must this be a manual
operation?
I generally recommend against automagic cleanup of lock files from
dead sessions being a general default
snip
Apparently not. If I start an X session (using the standard menu item
under the start menu) and manually shut it down, the lock file is not
deleted.
On a clean shutdown, the process should clean up its lock files; if it
isn't, that needs to looked at and/or reported. The only caveat to
Marco Atzeri wrote:
On 12/12/2014 7:07 PM, Will Parsons wrote:
For several years now I have been starting X windows by clicking on an
icon on my desktop that is a link to C:\cygwin\bin\startxwin.exe. It
has recently ceased to work because apparently startxwin.exe no longer
exists. Somehow
apparently startxwin.exe no longer
exists. Somehow I missed where this was removed, so what is the
recommended way of starting X from a desktop icon now?
I seem to recall that startxwin.exe was introduced some time ago
because using a script to start X was inadequate somehow, but I don't
remember
ceased to work because apparently startxwin.exe no longer
exists. Somehow I missed where this was removed, so what is the
recommended way of starting X from a desktop icon now?
I seem to recall that startxwin.exe was introduced some time ago
because using a script to start X was inadequate
:\cygwin\bin\startxwin.exe. It
has recently ceased to work because apparently startxwin.exe no longer
exists. Somehow I missed where this was removed, so what is the
recommended way of starting X from a desktop icon now?
I seem to recall that startxwin.exe was introduced some time ago
because using
For several years now I have been starting X windows by clicking on an
icon on my desktop that is a link to C:\cygwin\bin\startxwin.exe. It
has recently ceased to work because apparently startxwin.exe no longer
exists. Somehow I missed where this was removed, so what is the
recommended way
16 matches
Mail list logo