Re: cygwin/1.3.20-1 bash child process disassociation behavior weirdness

[Christopher Faylor <cgf at redhat dot com>]

On Fri, Mar 07, 2003 at 06:17:17PM -0500, Igor Pechtchanski wrote:
>On Fri, 7 Mar 2003, Max Bowsher wrote:
>> Christopher Faylor wrote:
>> > On Fri, Mar 07, 2003 at 10:00:28PM -0000, Max Bowsher wrote:
>> >> Richard H. Broberg wrote:
>> >>> In non-cygwin unix I'm familiar with being able to do the following
>> >>> in a shell (bash or other):
>> >>>
>> >>> $ nohup long-running-command &
>> >>> $ exit
>> >>>
>> >>> and be able to leave it running.
>> >>>
>> >>> However, under cygwin (this has been true for at least back to
>> >>> cygwin/1.3.6 for me), when I start a process in the background and
>> >>> try to exit
>> >>> my bash shell, it hangs until the child process completes (almost as
>> >>> if it's doing a wait() on its children).
>> >>>
>> >>> Additionally, if I start a command nohup in the background in 1 bash
>> >>> shell and close the window, it kills the child process.
>> >>
>> >> An unfortunate consequence of how Windows handles console windows.
>> >
>> > This works for me:
>> >
>> > nohup sleep 30 </dev/null >foo 2>&1&
>> >
>> > at least with the latest version of cygwin...
>>
>> Doesn't work for me, running self-built cvs HEAD cygwin dll.
>>
>> By doesn't work, I mean:
>> I copy-paste the exact command above
>> I Ctrl-D
>> Bash exits, but the comsole window remains for 30 seconds.
>
>Could be a CYGWIN=tty issue...

I tried it both ways.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/