public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Erik Soderquist <ErikSoderquist@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: startxwin.exe no longer exists?
Date: Wed, 17 Dec 2014 18:36:00 -0000	[thread overview]
Message-ID: <CACoZoo3A7nfTLbesK==QGqporj+2RM1YxV6qg0hm34zBJETCTg@mail.gmail.com> (raw)
In-Reply-To: <f0cd88b0d4227baff5793410155de6d1@saf.bio.caltech.edu>

<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 have your
script hiding the fact that it crashed from you?

>
>>
>> Also, as the X server is not bound to a tty, it forks to the
>> background on its own anyway, so your pseudocode example would delete
>> the lock file just after the X server started.
>
>
> In that case the the script needs to retrieve the PID of the forked process
> and wait for it to exit.


I would much rather have the binary process clean up after itself like
it is supposed to, and figure out why the binary process is failing to
do so when it doesn't than have a script that hides such failures from
me.

To each its own though.

-- Erik

--
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/


  reply	other threads:[~2014-12-17 18:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13 16:20 Will Parsons
2014-12-13 18:17 ` Marco Atzeri
2014-12-16  2:50   ` Will Parsons
2014-12-16  2:56     ` Larry Hall (Cygwin-X)
2014-12-16  3:30       ` Will Parsons
2014-12-16  3:35         ` Larry Hall (Cygwin-X)
2014-12-16 14:29     ` Mark Hansen
2014-12-16 16:00     ` Erik Soderquist
2014-12-16 16:36       ` rcunningham
2014-12-16 17:06         ` Erik Soderquist
2014-12-16 17:23           ` rcunningham
2014-12-16 22:58           ` Will Parsons
2014-12-16 23:39             ` Erik Soderquist
2014-12-17 17:29               ` mathog
2014-12-17 17:40                 ` Erik Soderquist
2014-12-17 17:52                   ` mathog
2014-12-17 18:36                     ` Erik Soderquist [this message]
2014-12-17 19:02                       ` mathog

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACoZoo3A7nfTLbesK==QGqporj+2RM1YxV6qg0hm34zBJETCTg@mail.gmail.com' \
    --to=eriksoderquist@gmail.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).