This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

nohup hanging up


Hi All,

I have strong evidence that the nohup utility provided with Cygwin
actually does permit inappropriate hangups. Instead of success and a
running process, my process is gone and all I get where my process was is
<defunct>. I'm hoping to learn that I've misinterpreted the evidence...

My application wants to start an ssh port-forwarding process (hence my
most recent posts on that subject) which needs to hang around while
another process keeps a database connection going. Because of the
construction of the application, nohup is needed since the ssh process
can't be started directly from the applicationn. Running on a real unix
platform, the existing application architecture works perfectly. It sure
would be nice to run _one_ architecture and avoid a second one for
Windows/cygwin!

...There's absolute certainty that my app follows the rules, applying &
itself, and directing output to an approprite, existing output file, etc.
The code is well debugged on Unix/Linux. I invite comments on Cygwin
details in this regard. Why does Cygwin's version tear down the child when
the parent goes away? What, if anything can I do about it?

Regards,
Richard

-- 
Richard Troy, Chief Scientist
Science Tools Corporation
rtroy at ScienceTools dot com, 510-567-9957, http://ScienceTools.com/



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]