Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Sep 2001 11:35:30 -0700
From:      Sean Chittenden <sean@chittenden.org>
To:        Peter Pentchev <roam@ringlet.net>
Cc:        Neil Blakey-Milner <nbm@FreeBSD.org>, freebsd-ports@FreeBSD.org
Subject:   Re: sysutils/daemontools FreeBSD port update to 0.76
Message-ID:  <20010902113530.B42588@rand.tgd.net>
In-Reply-To: <20010901165256.A2365@ringworld.oblivion.bg>; from "roam@ringlet.net" on Sat, Sep 01, 2001 at = 04:52:56PM
References:  <20010901165256.A2365@ringworld.oblivion.bg>

next in thread | previous in thread | raw e-mail | index | archive | help
> The attached patch updates the daemontools port to 0.76.
> My machine has been running with it for the past few days,
> and everything seems to be working fine so far.

	Excellent!

> The one drawback I see is that this deviates from DJB's instructions
> by not using the svscanboot script for svscan startup, and consequently,
> not running readproctitle for the ability to glance quickly at svscan's
> error output.  svscanboot, however, has a hardcoded path for /service,
> and is therefore slightly inferior to our own svscan.sh :)
> 
> Should I try to modify svscan.sh to run readproctitle, or modify
> svscanboot to honor a variable /service path, or just leave it
> the way it is

	Modify svscan.sh and svscanboot?  Given that most FreeBSD folks
will probably use svscan.sh (haven't seen an exception yet), I'd put
that as the higher priority.  If you patch svscanboot, then that'd be
icing one the cake, but not as useful as the modified svscan.sh.  
Leaving things as is would cause a world of problems, IMHO.  Having 
svscan work out of the box is what people expect and they don't 
necessarily care how it works (and if they do, then they're probably 
wise/experienced enough to figure it out).  Maybe a pkg-message is in 
order?

> (which would incur DJB's wrath when problems are
> reported back, lacking readproctitle's output..) ?

	Blah, his crankiness is his own fault: don't cater to it.

> Should any of this be committed before 4.4 hits the streets? :)

	Most certainly!  ;)  -sc

-- 
Sean Chittenden

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010902113530.B42588>