Some local rc scripts running twice
oberman at es.net
Mon May 28 18:03:47 UTC 2007
> Date: Sun, 27 May 2007 16:34:19 -0300
> From: Duane Whitty <duane at dwlabs.ca>
> Sender: owner-freebsd-stable at freebsd.org
> Hi Pascal,
> Much thanks!
> On Sunday, 27 May 2007 at 14:11:13 +0200, Pascal Hofstee wrote:
> > On Sun, 2007-05-27 at 03:48 -0300, Duane Whitty wrote:
> > > Has anyone else encountered local rc scripts running
> > > twice? I thought I saw something about this on one
> > > of the @freebsd.org lists but my search efforts haven't
> > > located it yet.
> > In assuming "local rc scripts" means anything installed by ports ... i
> > am assuming you installed a fresh Xorg-7.2 and now at some point ended
> > up with the /usr/X11R6 -> /usr/local symlink.
> > If the above assumption holds true ... did you run the mergebase.sh
> > script as suggested in /usr/ports/UPDATING ?
> The above assumptions are correct and mergebase.sh did run.
> > Most significantly .. this script adds the following entry to
> > your /etc/rc.conf
> > local_startup="/usr/local/etc/rc.d"
> This was the problem. Adding this to my /etc/rc.conf manually
> fixed everything up for me. Thanks!
> > The default entry in /etc/defaults/rc.conf still
> > references /usr/X1R6/etc/rc.d as well ... since the latter is now a
> > symlink to the former, both rc.d-paths contain the same scripts.
> > If your rc.conf doesn't contain the aforementioned entry, that would
> > explain why local rc-scripts are started twice.
> Yeah, that does it explain it. The mergebase.sh script failed
> unfortunately and I needed to take manual steps to complete
> the upgrade process.
> When the script failed due to conflicting files I deleted the
> files that were listed, re-ran the script, got the same conflicts,
> and then created the symlink myself. Unfortunately, the rc.conf
> entry didn't get added as well. I am left wondering if other
> things that were supposed to happen did not happen.
> When operator error complicates matters, as it has in this case,
> no script can deal with all possible scenarios. So, to all the
> people who worked on making this upgrade happen, please don't
> take this as a criticism of the script or upgrade process
If ./etc is mounted read-only, the file is not updated and I got no
warning about the failure from the script. As a result I need to
hand-edit both rc.conf and periodic to fix stuff properly.
I don't suspect having a RO /etc is all that common, but I am sure
others will hit this, too.
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 224 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070528/9a331e8e/attachment.pgp
More information about the freebsd-stable