On Friday 30 April 2004 11:52, Ben Stringer wrote:
> On Fri, 2004-04-30 at 18:42, Doncho N. Gunchev wrote:
> > >
> > > How do I prevent this?
> > How did you get this? I could not reproduce it - my xclock stays.
>
> This was my initial re-action too. Then I found that exit/CNTL-D in the
> terminal left the xclock around, but using the "X" window decoration to
^^^^^^^^^^^^^^^^^ indeed, it does !?!
> kill it caused the xclock to die also.
Hmm, this is *VERY* strange, but it's true. If you use
$ (xclock < /dev/null > /dev/null 2>&1 &)&
AND press <ENTER> once it will live, but whatever you do if you do not
press <ENTER> it dies! The same things happen with konsole also.
If you do:
((xclock < /dev/null > /dev/null 2>&1 &)&); /bin/true
there's no problem, which made me think it is bash related isue. Even
simple '(xclock&) ; /bin/true' works (xclock does not get killed).
If you 'xterm -e tcsh', to use tcsh instead of bash - there is no
problem. Should we repport this as a bug or is this bash feature?
I think this is bug.
Can someone from RedHat developers please clarify the situation?
--
Regards,
Doncho N. Gunchev Registered Linux User #291323 at counter.li.org
GPG-Key-ID: 1024D/DA454F79
Key fingerprint = 684F 688B C508 C609 0371 5E0F A089 CB15 DA45 4F79
