This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Re: [cygrunsrv] problem starting exim as service
- From: Igor Peshansky <pechtcha at cs dot nyu dot edu>
- To: Karl M <karlm30 at hotmail dot com>
- Cc: cygwin at cygwin dot com
- Date: Tue, 13 Mar 2007 11:15:31 -0400 (EDT)
- Subject: Re: Re: [cygrunsrv] problem starting exim as service
- References: <BAY125-F5FC8A4E10426BD726A807B57C0@phx.gbl>
- Reply-to: cygwin at cygwin dot com
Ugh, top-posting... Reformatted.
On Tue, 13 Mar 2007, Karl M wrote:
> > From: "Wynfield Henman" Subject: Re: Re: [cygrunsrv] problem starting exim
> > as service
> > Date: Tue, 13 Mar 2007 14:31:41 +0900
> >
> > [snip]
> > I believe that it should show this process as running (but
> > some say that exim detaches itself and so cygrunsrv can't know about
> > it).. if would know if it did a process check, but that's another
> > matter..
>
> Hi All...
>
> Cygrunsrv needs the process to stay attached so it can keep track of it
> for you. Services are managed differently on Windows than on *ix.
That's not quite true. Yes, the SCM (Windows' Service Control Manager)
does need a process to be attached, but that process is cygrunsrv, not the
program running as service.
> Exim has command line options to allow this (-bdf instead of -bd). I've
> never used exim, but looked in the FAQ.
>
> If you can't keep exim from detaching, you can create a wrapper script
> around exim that does not detach. This can be as simple or fancy (keep
> track of the pid for signalling) as you like.
Cygrunsrv already has support for this. Take a look at the --pidfile
option.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Freedom is just another word for "nothing left to lose"... -- Janis Joplin
--
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/