X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=BAYES_00,DKIM_ADSP_NXDOMAIN,NO_DNS_FOR_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Subject: nohup, non-cygwin processes From: "Matthew B. Smith" To: cygwin AT cygwin DOT com In-Reply-To: <1270469274.15260.ezmlm@cygwin.com> References: <1270469274 DOT 15260 DOT ezmlm AT cygwin DOT com> Content-Type: text/plain; charset="UTF-8" Date: Mon, 05 Apr 2010 08:22:09 -0400 Message-ID: <1270470129.16102.11.camel@erebor> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hello 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. 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) thank you mbs -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple