From nobody@FreeBSD.org  Tue Jun 27 02:01:50 2006
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 51B0716A407
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 27 Jun 2006 02:01:50 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DDD8143D78
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 27 Jun 2006 02:01:45 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k5R21jOd007838
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 27 Jun 2006 02:01:45 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k5R21jkF007837;
	Tue, 27 Jun 2006 02:01:45 GMT
	(envelope-from nobody)
Message-Id: <200606270201.k5R21jkF007837@www.freebsd.org>
Date: Tue, 27 Jun 2006 02:01:45 GMT
From: Cristopher Atienza <cfatienza@yahoo.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: /usr/local/etc/rc.d script files won't load during bootup via Diskless
X-Send-Pr-Version: www-2.3

>Number:         99515
>Category:       conf
>Synopsis:       /usr/local/etc/rc.d script files won't load during bootup via Diskless
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    yar
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jun 27 02:10:19 GMT 2006
>Closed-Date:    Sun Mar 02 02:52:39 UTC 2008
>Last-Modified:  Sun Mar 02 02:52:39 UTC 2008
>Originator:     Cristopher Atienza
>Release:        FreeBSD 6.1 Release
>Organization:
>Environment:
FreeBSD latitude 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Fri Jun 23 11:11:04 PHT 2006     cfa@hp.decorp.com.ph:/usr/src/sys/i386/compile/CUSTOM  i386
>Description:
I have FreeBSD 6.1 release diskless server serving 10 Diskless client
machines same version from the server. The problem is that when the
diskless client bootup all the script on /usr/local/etc/rc.d would not
load properly without any error messages. Why is it like that while the
diskless server loaded all the script on /usr/local/etc/rc.d. 

btw: I have also several machines running on FreeBSD 6.1 release like
laptops and desktops without any problem on bootup all the script are
being loaded properly. Here are the following script on my /usr/local/etc/rc.d.

000.compat4x
000.compat5x
000.grass.sh
000.wine.sh
cupsd
dbus
hylafax.sh.sample
mdnsresponder.sh
rsyncd
samba.sh

note: I have entered the following lines to my /etc/rc.conf file.

compat4x_enable="YES"
compat5x_enable="YES"
cupsd_enable="YES"
samba_enable="YES"
dbus_enable="YES"


others: I have notice that booting from diskless even usbd_enable="YES"
won't work but as I have said booting from local no problem at all. What
is the reason  behind this? from my FreeBSD 6.0 release before I have no
problem like this.

regards,
cris  

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: yar 
State-Changed-When: Fri Aug 17 09:15:02 UTC 2007 
State-Changed-Why:  
I think that there has beem a new way of handling local rc.d scripts 
since 6.1-RELEASE.  From the rc.conf(5) manpage: 

early_late_divider 
(str) The name of the script that should be used as the 
delimiter between the ``early'' and ``late'' stages of the 
boot process.  The early stage should contain all the ser- 
vices needed to get the disks (local or remote) mounted so 
that the late stage can include scripts contained in the 
directories listed in the local_startup variable (see below). 
Thus, the two likely candidates for this value are 
mountcritlocal for the typical system, and mountcritremote if 
the system needs remote file systems mounted to get access to 
the local_startup directories; for example when /usr/local is 
NFS mounted.  For rc.conf within a jail(8) NETWORKING is 
likely to be an appropriate value.  Extreme care should be 
taken when changing this value, and before changing it one 
should ensure that there are adequate provisions to recover 
from a failed boot (such as physical contact with the 
machine, or reliable remote console access). 

In your case, setting the variable to "mountcritremote" seems necessary. 
Please report back if it helps. 


Responsible-Changed-From-To: freebsd-bugs->yar 
Responsible-Changed-By: yar 
Responsible-Changed-When: Fri Aug 17 09:15:02 UTC 2007 
Responsible-Changed-Why:  
So I can see feedback. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=99515 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Sun Mar 2 02:52:20 UTC 2008 
State-Changed-Why:  
Feedback timeout (> 6 months). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=99515 
>Unformatted:
