Re: Lindows programs unexpectantly closing

Chris F.A. Johnson wrote:
On 2007-06-29, sk8r-365 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.

Then they are not sending anything to stdout or stderr. Putting
them in the background or not will make no difference.

i agree
some programs dont even open the necessary file handles to even report stdout and stderr back to the terminal
check this by cat /proc/process_id/fd/* if they don't have a console or pseudo console
as file handle then they can't even report back to the term that has started it

you can however start a process in background with a parent process that's a subshell like this
( command &)

if you do that then yes it won't report back to the terminal the command was typed in
.

Relevant Pages

  • Re: test whether stdout==stderr?
    ... > By default the shell attaches stdout and stderr to the same device, ... Actually it isn't the shell that does this. ...
    (comp.os.linux.development.apps)
  • Re: test whether stdout==stderr?
    ... >> By default the shell attaches stdout and stderr to the same device, ... > Actually it isn't the shell that does this. ...
    (comp.os.linux.development.apps)
  • Re: Lindows programs unexpectantly closing
    ... anything it sends to stdout or stderr will appear in that shell. ... Then they are not sending anything to stdout or stderr. ... if you do that then yes it won't report back to the terminal the command ...
    (alt.os.linux)
  • Re: test whether stdout==stderr?
    ... >> By default the shell attaches stdout and stderr to the same device, ... > Actually it isn't the shell that does this. ... You could do some tests with lseek() to see if changing one descriptor ...
    (comp.os.linux.development.apps)
  • FAQ 8.25 How can I capture STDERR from an external command?
    ... This message is one of several periodic postings to comp.lang.perl.misc ... both STDOUT and STDERR will go the same place as the ... script's STDOUT and STDERR, unless the systemcommand redirects them. ... You can also use file-descriptor redirection to make STDERR a duplicate ...
    (comp.lang.perl.misc)