From owner-freebsd-stable@FreeBSD.ORG Tue Jan 10 11:59:35 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FECA16A420 for ; Tue, 10 Jan 2006 11:59:35 +0000 (GMT) (envelope-from marko@freebsd.org) Received: from pih-relay05.plus.net (pih-relay05.plus.net [212.159.14.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55E5B43D46 for ; Tue, 10 Jan 2006 11:59:33 +0000 (GMT) (envelope-from marko@freebsd.org) Received: from [80.229.231.20] (helo=[192.168.1.4]) by pih-relay05.plus.net with esmtp (Exim) id 1EwI9z-00089W-L9 for stable@freebsd.org; Tue, 10 Jan 2006 11:59:32 +0000 Message-ID: <43C3A1DE.10203@freebsd.org> Date: Tue, 10 Jan 2006 12:00:30 +0000 From: Mark Ovens User-Agent: Mail/News 1.6a1 (X11/20051228) MIME-Version: 1.0 To: stable@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: recent rc changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2006 11:59:35 -0000 Charles Sprickman wrote: > Hello, > > I recently made the jump to -stable from 6.0 on a box that I'm looking to > bring into production as soon as 6.1 hits. Everything seems fine so far > but for one issue that I am guessing is related to the rc changes in > -stable. > > This host has two jails, both started via the rc.conf method, ie: > > # jail stuff - general > jail_enable="YES" > jail_list="somejail somejail2" > jail_socket_unixiproute_only="YES" > jail_sysvipc_allow="NO" > # jail stuff - per jail settings > # jail 1 - shell > jail_jail1_rootdir="/jails/somejail" > jail_jail1_hostname="somejail.bway.net" > jail_jail1_ip="216.220.x.x" > jail_jail1_exec_start="/bin/sh /etc/rc" > jail_jail1_exec_stop="/bin/sh /etc/rc.shutdown" > jail_jail1_devfs_enable="YES" > jail_jail1_fdescfs_enable="NO" > jail_jail1_procfs_enable="NO" > jail_jail1_mount_enable="NO" > jail_jail1_devfs_ruleset="devfsrules_jail" > > Since the upgrade, I've noticed that none of the ports-installed services > in each jail start up. For example, both jails have apache2 and > mysql40-server installed. Everything in /usr/local/etc/rc.d within each > jail looks correct, and the startup flags are set in each jail's rc.conf. > They start fine if I login to the jail and run the scripts, but do not > start at boot. See the thread "FreeBSD Port: sysutils/smartmontools (more RCng problems)" in -ports, particularly the posts by Doug Barton. It sounds like the same problem. I used his fix to get a couple of daemons to start at boot which had stopped doing so after u/g to 6.0. ------ quote Doug Barton -------- Ok, I installed this port and tested it myself, and the problem is the hard coded value of smartd_enable at the top of the script. For reasons I don't quite understand yet, hard coding the value in the script affects the boot-time operation of the script differently than on the command line. The good news is that the fix is simple: Index: smartd.sh =================================================================== RCS file: /home/pcvs/ports/sysutils/smartmontools/files/smartd.sh,v retrieving revision 1.5 diff -u -r1.5 smartd.sh --- smartd.sh 18 Nov 2005 11:46:38 -0000 1.5 +++ smartd.sh 6 Jan 2006 23:36:35 -0000 @@ -13,8 +13,8 @@ # # DO NOT CHANGE THESE DEFAULT VALUES HERE # -smartd_enable="NO" -smartd_pidfile="/var/run/smartd.pid" +smartd_enable=${smartd_enable:-NO} +smartd_pidfile=${smartd_pidfile:-/var/run/smartd.pid} . %%RC_SUBR%% ------ quote Doug Barton -------- HTH Regards, Mark