This is the mail archive of the
mailing list for the Cygwin project.
RE: nohup, non-cygwin processes
- From: "Jason Pyeron" <jpyeron at pdinc dot us>
- To: <cygwin at cygwin dot com>
- Date: Mon, 5 Apr 2010 08:50:34 -0400
- Subject: RE: nohup, non-cygwin processes
- References: <firstname.lastname@example.org> <1270470129.16102.11.camel@erebor>
> -----Original Message-----
> From: Matthew B. Smith
> Sent: Monday, April 05, 2010 8:22
> Subject: nohup, non-cygwin processes
> I am writing about a problem probably not due to cygwin, but
> I think it used to work with 1.5.
> I want to start a long running process with nohup and have it
> continue to run even though I log out of the computer. It
> seems no matter how I start the process I get a SYGTERM
> signal when I log out of windows.
> This is a 64-bit java program but I seem to remember being
> able to do this with nohup prior to upgrading to cygwin 1.7.
It's a JVM issue, start the JVM with the parameter -Xrs to ignore this
Logoff event signal.
> As an example if I login via ssh and start the process, it is
> fine and I can log out, then log back in, but as soon as a
> user logs out of windows it will terminate the java job.
> This will happen even if I am ssh'd in with the process
> running. (which is how I found the exit code 143)
$ java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
$ java -X
-Xrs reduce use of OS signals by Java/VM (see documentation)
The -X options are non-standard and subject to change without notice.
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
This message is copyright PD Inc, subject to license 20080407P00.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple