From owner-freebsd-arch Tue Jun 18 1:29:17 2002 Delivered-To: freebsd-arch@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 95EE537B40F for ; Tue, 18 Jun 2002 01:29:11 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.36 #1) id 17KEMn-0000CN-00; Tue, 18 Jun 2002 10:29:33 +0200 From: Sheldon Hearn To: Mike Makonnen Cc: arch@FreeBSD.ORG Subject: Re: rcNG rollout in -current In-reply-to: Your message of "Mon, 17 Jun 2002 16:51:37 MST." <20020617165137.65962cff.makonnen@pacbell.net> Date: Tue, 18 Jun 2002 10:29:32 +0200 Message-ID: <766.1024388972@axl.seasidesoftware.co.za> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 17 Jun 2002 16:51:37 MST, Mike Makonnen wrote: > > I'm about to try my first rcNG bootstrap. I'm confident that there are > > lots of people who, like me, are much more likely to test stuff if it's > > in the tree and just requires the flick of a switch to turn on and off. > > Cool, give us some feedback (positive or otherwise). First the otherwise feedback. :-) | /etc/rc: INFO: mountd depends on rpcbind, which will be forced to start. | Starting rpcbind. | Starting mountd. | /etc/rc: WARNING: $portmap_enable is not set. Historically, we've been allowed to have portmap_enable="NO" (which is what I have) and rest assured that it would be started as a dependency. For this reason, the WARNING seems unnecessary. Regardless, $portmap_program (rpcbind) is started correctly and 'showmount -e' indicates that mountd is working. | /etc/rc: WARNING: $sendmail_enable is not set properly. I think you alreday know about this one, but I'm not sure. The WARNING appears harmless -- sendmail was not started, which is what I wanted with sendmail_enable="NONE". | Starting named. | can't open 'rc_flags' | Jun 18 09:57:42 axl named[269]: can't open 'rc_flags' This is with named_rcng="YES" added to my existing named_enable="YES" and named_flags="-u bind -g bind". Looks like a simple typo in etc/rc.d/named: Index: named =================================================================== RCS file: /home/ncvs/src/etc/rc.d/named,v retrieving revision 1.2 diff -u -d -r1.2 named --- named 13 Jun 2002 22:14:36 -0000 1.2 +++ named 18 Jun 2002 08:00:49 -0000 @@ -84,7 +84,7 @@ ! checkyesno named_rcng && return 0 # Is the user using a sandbox? if [ -z "$named_chrootdir" ]; then - rc_flags="-u $nuser -g $ngroup rc_flags" + rc_flags="-u $nuser -g $ngroup $rc_flags" return 0 fi I see that the way etc/rc.d/named works, named_flags="-u bind -g bind" is no longer required. So finally we have sane defaults there. Cool. With this patch applied, named starts. The next step is to add named_chrootdir="/etc/named/s", where /etc/named/s and the appropriate subdirectories exist. Then, at least one required file is not copied into the chrootdir, namely etc/namedb/named.conf. Others, like etc/resolv.conf should probably be copied in as well, but this gets tricky. What if there are zone files? So it looks like the named_chrootdir idea needs a bit more thought. Unfortunately, I can't do the thinking right now. And now for the positive feedback. :-) I'm _very_ impressed. I'm really glad you persevered, really glad you listened to David O'Brien and really excited about where you've brought us to, to say nothing of where this means we can go! Good job! Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message