Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 16 Jul 2001 17:19:08 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Cc: Fred Yankowski , pgsql-cygwin@postgresql.org Subject: Re: [ANNOUNCEMENT] Updated: cygrunsrv-0.94-1 Message-ID: <20010716171908.V25442@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com, Fred Yankowski , pgsql-cygwin@postgresql.org References: <20010712114208.A11408@enteract.com> <20010716100417.D561@dothill.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010716100417.D561@dothill.com>; from Jason.Tishler@dothill.com on Mon, Jul 16, 2001 at 10:04:17AM -0400 On Mon, Jul 16, 2001 at 10:04:17AM -0400, Jason Tishler wrote: > Fred, > > On Thu, Jul 12, 2001 at 11:42:08AM -0500, Fred Yankowski wrote: > > On Thu, Jul 12, 2001 at 11:45:39AM -0400, Jason Tishler wrote: > > > Please post your patch -- I've been waiting with bated breath since you > > > first mentioned it. :,) I will be quite willing to champion it (or a > > > better solution, if one can be devised) for inclusion into PostgreSQL CVS. > > > > OK, here's the patch. It's crude, simply causing the SIGHUP handlers > > (one for postmaster and one for postgres) to return immediately > > without triggering the normal config-file-reloading response. > > What about trying to tackle this from another point of view? I'm not > sure if this is doable or acceptable, but what about adding logic to the > Cygwin DLL so that it does not send SIGHUP (to itself) when the process is > running under cygrunsrv? Hmmm, sounds like an ugly hack to me... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/