From owner-freebsd-ports Sun Sep 2 11:35:38 2001 Delivered-To: freebsd-ports@freebsd.org Received: from mail.tgd.net (rand.tgd.net [64.81.67.117]) by hub.freebsd.org (Postfix) with SMTP id EEBF237B403 for ; Sun, 2 Sep 2001 11:35:34 -0700 (PDT) Received: (qmail 42813 invoked by uid 1001); 2 Sep 2001 18:35:31 -0000 Date: Sun, 2 Sep 2001 11:35:30 -0700 From: Sean Chittenden To: Peter Pentchev Cc: Neil Blakey-Milner , freebsd-ports@FreeBSD.org Subject: Re: sysutils/daemontools FreeBSD port update to 0.76 Message-ID: <20010902113530.B42588@rand.tgd.net> References: <20010901165256.A2365@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010901165256.A2365@ringworld.oblivion.bg>; from "roam@ringlet.net" on Sat, Sep 01, 2001 at = 04:52:56PM X-PGP-Key: 0x1EDDFAAD X-PGP-Fingerprint: C665 A17F 9A56 286C 5CFB 1DEA 9F4F 5CEF 1EDD FAAD X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > 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