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. I believe it would be possible to write an alternative implementation of nohup using fork/setsid, or perhaps even hack some changes into the Cygwin DLL. But it's now just a configuration issue - it will take some coding. Max. -- 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/