From owner-freebsd-questions@FreeBSD.ORG Wed Dec 31 11:14:53 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9DAB16A4CE for ; Wed, 31 Dec 2003 11:14:53 -0800 (PST) Received: from dyer.circlesquared.com (host217-45-219-83.in-addr.btopenworld.com [217.45.219.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEC7143D1D for ; Wed, 31 Dec 2003 11:14:46 -0800 (PST) (envelope-from peter@circlesquared.com) Received: from circlesquared.com (localhost.petanna.net [127.0.0.1]) hBVJDEdA002129; Wed, 31 Dec 2003 19:13:26 GMT (envelope-from peter@circlesquared.com) Message-ID: <3FF31FCA.4040805@circlesquared.com> Date: Wed, 31 Dec 2003 19:13:14 +0000 From: Peter Risdon User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20031102 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ion-Mihai Tetcu References: <20031230034953.36866d74@it.buh.cameradicommercio.ro> <200312300225.hBU2PQsi030000@smtp.doruk.net.tr> <20031230043149.73c3dddd@it.buh.cameradicommercio.ro> <3FF15920.4070201@circlesquared.com> <20031231004933.00b76790@it.buh.cameradicommercio.ro> In-Reply-To: <20031231004933.00b76790@it.buh.cameradicommercio.ro> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: djbdns X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2003 19:14:53 -0000 Ion-Mihai Tetcu wrote: >On Tue, 30 Dec 2003 10:53:20 +0000 >Peter Risdon wrote: > > > >>Ion-Mihai Tetcu wrote: >> >> >> >>>Take a look at /usr/local/etc/rc.d/svscan.sh.sample >>> >>>1. SVDIR=/var/service/ - so svscan will look at /var/service and not >>>/service; either do: >>>a) what is suggested and use /var/services (e.g. ln -s /etc/dnscache >>>/var/service) or >>>b) change SVDIR=/var/service/ to SVDIR=/service/ >>> >>>I would use a); also note that creating the log file in /etc/dnscache >>>is IMHO a bad idea. >>> >>> >>> >>> >>I'm not disagreeing, but the original post complained of something >>being wrong in some documentation. >> >> > >Yes, the idea of logging to / is bad at least for 2 reasons: filling up >/, which is usually small and, in case of a crash, increasing the >chances to have a trashed / > > In passing, I don't understand why any dns data are stored in subdirectories of /etc and not /var. But while this is important for the log files, the service directory just contains soft links, so no issues of disk space arise from a location in /. It seems to be more a matter of how you read hier(7). >>Most reference and tutorial pages for >>djbdns and other djb stuff like qmail assume a /service directory, >>rather than /var/service. >> >> > >I've always loved the explanation "Portability. With /service, your >program works the same way on every system: Linux, BSD, Solaris, etc." >(http://cr.yp.to/daemontools/faq/create.html#run); using this logic >every program should install in his own directory in / > > Not entirely: daemontools has a broad application to other services that most programs lack. As a, sort of, replacement for inet.d it has a different status to, say, mozilla. One /service directory allows more than one daemon to run. I'm all for standardisation of file locations across unixen. There's just the small matter of agreeing what those standard locations should be. >>Using /var/service does seem more logical, but >>can be a source of confusion, especially if people are copying and >>pasting commands from online instructions, something the various >>references often suggest. >> >> > >Perhaps I should suggest to the maintainer adding a pkg-message saying >that, by default, we're using /var/services ? > > Good idea, though there is already a mention of this issue in /usr/local/etc/rc.d/svscan.sh.sample I think the djbdns and the qmail ports should create the service directory if it's not already there (in / or /var, whatever, so long as both ports agree) and the symlinks within it, with configure options for selecting a different location. That would help avoid a lot of confusion and mean the ports installed services that were actually capable of running after the make install without an unusual amount of tweaking, but I'll take this to the relevant list. PWR