Re: Lindows programs unexpectantly closing



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.
--
sk8r-365

http://goodbye-microsoft.com/
.



Relevant Pages

  • Inappropriate ioctl for device when calling tcsetpgrp() on Solaris
    ... I'm writing a shell program that will do background/foreground executions. ... On Solaris, when I put a child process to background, I use tcsetpgrp(fd, ... shell_pgrp_id) to let my shell have the control of terminal. ...
    (comp.unix.programmer)
  • Re: Lindows programs unexpectantly closing
    ... shell will not have that app as a child process. ... A background process *is* a child of the shell that spawned it, ... gnomesword 2.1.9-1 crashes without any output messages either to console ...
    (alt.os.linux)
  • Re: Lindows programs unexpectantly closing
    ... shell will not have that app as a child process. ... gnomesword 2.1.9-1 crashes without any output messages either to console ...
    (alt.os.linux)
  • RE: environment variable
    ... The standard Unix semantics is this: a child process inherits the ... The shell also takes a series of zero or more key-value pairs ... intended for the named addressee (or a person responsible for delivering it to ... If you are not the intended recipient of this message, ...
    (perl.dbi.users)
  • Tracking background children processes and cleaning up "zombies"
    ... there is a special command in my shell ... a command that runs another command/executable program ... I did a forkand an execto run the child process ... background processes are like runaway trains which I've no control ...
    (comp.unix.programmer)