[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
somthing wrong with disown?
From: |
Michael Lashkevich |
Subject: |
somthing wrong with disown? |
Date: |
Sun, 29 Jun 2003 22:57:03 +0400 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030309 |
I use the version
GNU bash, version 2.05.8(1)-release (i386-redhat-linux-gnu)
When I am starting a command through bash from Nedit shell menu or
Midnight Commander extension file, e.g.
xdvi filename &>/dev/null & disown
the launched ("xdvi" here) command still remains to be dependent of the
parent application (e.g. it crushes when I stop Nedit or MC).
The "csh" does not have this problem. For example, if I use "csh" as
default shell started for Nedit/MC the command
xdvi filename >&/dev/null &
or start it through an auxiliary "csh" like
csh -c "xdvi filename >&/dev/null" &>/dev/null
it works properly. From reading Nedit FAQs, I may suppose that something
is wrong with releasing file descriptors of disowned background commands.
Best regards,
Michael Lashkevich
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- somthing wrong with disown?,
Michael Lashkevich <=