I just tried re-building postgres for cygwin, using patches only to
ignore SIGHUP and not my other service-management cruft.
Unfortunately, testing shows that this doesn't suffice to get postgres
to start up cleanly after NT restart when run under cygrunsrv. The
postmaster.pid file is still left around.
My plan to create a patch for cygrunsrv that allows it to send a
signal to the managed service process when it (cygrunsrv) is notified
that NT is shutting down.
Note that someone else on the Cygwin email list reports occasional
problems where cygrunsrv completely fails to start after NT restart.
In their case they're using it for sshd, not postgres, but even so I'm
somewhat concerned that cygrunsrv may have some timing-related
On Fri, Jun 15, 2001 at 08:53:33AM +0100, Henshall, Stuart - WCP wrote:
> Thanks for the info, do you have a patch for ignoring SIGHUP? If not I guess
> it'll be time to delve into the source :).
Fred Yankowski fred(at)OntoSys(dot)com tel: +1.630.879.1312
Principal Consultant www.OntoSys.com fax: +1.630.879.1370
OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA
In response to
pgsql-cygwin by date
|Next:||From: Fred Yankowski||Date: 2001-06-15 19:47:56|
|Subject: cygrunsrv patch for system shutdown handling|
|Previous:||From: Jason Tishler||Date: 2001-06-15 16:49:04|
|Subject: Cygwin contrib patch|