Bug 99515

Summary: /usr/local/etc/rc.d script files won't load during bootup via Diskless
Product: Base System Reporter: Cristopher Atienza <cfatienza>
Component: confAssignee: Yar Tikhiy <yar>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Cristopher Atienza 2006-06-27 03:10:19 UTC 
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
Comment 1 Yar Tikhiy freebsd_committer freebsd_triage 2007-08-17 10:15:02 UTC 
State Changed
From-To: open->feedback

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.
Comment 2 Yar Tikhiy freebsd_committer freebsd_triage 2007-08-17 10:15:02 UTC 
Responsible Changed
From-To: freebsd-bugs->yar

So I can see feedback.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2008-03-02 02:52:20 UTC 
State Changed
From-To: feedback->closed

Feedback timeout (> 6 months).