Re: Lindows programs unexpectantly closing
- From: Davorin Vlahovic <nrubA@xxxxxxxxxxxxxx>
- Date: Fri, 29 Jun 2007 21:07:37 +0000 (UTC)
On 2007-06-29, sk8r-365 <sk8r-365@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Chris F.A. Johnson said:
On 2007-06-29, sk8r-365 wrote:
If you use '&' there is little likelihood for output because that
shell will not have that app as a child process.
A background process *is* a child of the shell that spawned it, and
anything it sends to stdout or stderr will appear in that shell.
Not always the case from what I've seen. Had a problem with gphoto2
a while ago - I use a card reader now because of it - and _no_ error
messages appeared *anywhere* I searched to indicate why the application
crashed when trying to access the camera. Plus, on Debian Etch,
gnomesword 2.1.9-1 crashes without any output messages either to console
or .xsession-errors when executed without or without an ampersand.
Start it in xterm/konsole/rxvt/whatever and see. Alternatively, start it
with "strace whatever".
--
"The idea that Bill Gates has appeared like a knight in shining armour
to lead all customers out of a mire of technological chaos neatly
ignores the fact that it was he who, by peddling second-rate technology,
led them into it in the first place." -- Douglas Adams
.
- References:
- Lindows programs unexpectantly closing
- From: Pete
- Re: Lindows programs unexpectantly closing
- From: beowulf@xxxxxxxxxxxx
- Re: Lindows programs unexpectantly closing
- From: sk8r-365
- Re: Lindows programs unexpectantly closing
- From: Chris F.A. Johnson
- Re: Lindows programs unexpectantly closing
- From: sk8r-365
- Lindows programs unexpectantly closing
- Prev by Date: Re: Lindows programs unexpectantly closing
- Next by Date: Re: Lindows programs unexpectantly closing
- Previous by thread: Re: Lindows programs unexpectantly closing
- Next by thread: Re: Lindows programs unexpectantly closing
- Index(es):
Relevant Pages
|