[Zope-Coders] Signal forwarding

[Chris McDonough]

Yeah, I can see that desire...

I think we're going to leave it "as is" for 2.6.0 (where the pidfile
always gets written into CLIENT_HOME/var), but then make it specifiable
via a config file option in later Zope versions (adding new envvars or
command-line switches is sort of pointless at the moment).

On Wed, 2002-10-09 at 09:23, Marius Gedminas wrote:
> On Tue, Oct 08, 2002 at 01:21:35PM -0400, Chris McDonough wrote:
> > Then again, I'm not sure about the utility of changing the pidfile name
> > if you can change CLIENT_HOME anyway, so maybe it shouldn't be
> > specifiable.  Would you ever want to change the location of a pid file
> > and *not* change it to a place where the associated instance's
> > filestorage files were?
> 
> Isn't /var/run/foo.pid recommended by the FHS or something?
> 
> I find it quite useful to have all pidfiles for all the system daemons
> in one place.  I have a shell script, callec check-health, which, among
> other things, loops over /var/run/*.pid and checks that every process
> mentioned there is running.  This catches a lot of cases where a system
> daemon dies without a proper cleanup.
> 
> Regards,
> Marius Gedminas
> -- 
> My opinions may have changed, but not the fact that I'm right!
> 
> _______________________________________________
> Zope-Coders mailing list
> Zope-Coders@zope.org
> http://lists.zope.org/mailman/listinfo/zope-coders