delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1997/05/02/20:18:22

From: scoleman AT sewp DOT nasa DOT gov (Steve Coleman)
Subject: NT services and gnu-win32
2 May 1997 20:18:22 -0700 :
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199705022019.QAA15288.cygnus.gnu-win32@mushroom.sewp.nasa.gov>
Reply-To: scoleman AT sewp DOT nasa DOT gov (Steve Coleman)
Mime-Version: 1.0
X-Mailer: exmh version 1.6.7 5/3/96
Original-To: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Hi,

I just downloaded the cygwin suite and ported my first Unix source code to NT 
yesterday and I was quite impressed with the ease at which I was able to do 
it. The program (a derivative of the TIS toolkit "smap") works fine from the 
command line but needs to run as a daemon on the system to be useful.  I then 
tried to use the NT resource kit (srvany.exe) to load the application as an NT 
service.  Everything works fine until someone logs out of the system at which 
time NT (sends messages? WM_ENDSESSION and CTRL_LOGOFF_EVENT) kills it. If the 
service is loaded when the machine boots the process still dies when the first 
person logs out.  Even the cygwin nohup.exe does not help.

Questions: Is there any way to trap/ignore this action within a cygwin 
application?  Compile options? Runtime signal processing? Special loading 
instructions for a service? 


Thanks.

Steve Coleman		scoleman AT sewp DOT nasa DOT gov
vox: 301.286.7636       fax: 301.286.0317



-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019