Re: Problems with source_rc_confs
On Fri, 2 Jun 2000, Alexander Leidinger wrote:
> I know, but I had to modify them to get it running.
If that's true, you already had some sort of custom modifications
which interfered with the way the system is supposed to work. That's not
"bad," it just makes debugging more complicated.
> I tried it with completely unmodified files just bevore my first mail to
> be sure it still didn't work.
If the files had been _completely_ unmodified, it would have
worked, assuming that your 5.0-Current is sufficiently up to date.
> I have the output of /etc/rc with "set -x" added to it, do you want it
> (together with rc.conf{,.local}) in a private mail (limited to 22k, my
> console hadn't more in the scrollback buffer)?
Actually, if you could send me this:
tar zcvf Alexander-rc.tgz /etc/rc* /etc/defaults/rc.conf
I may be able to get to the bottom of it. I wrote that function, and most
of the supporting stuff.
Doug
--
"Live free or die"
- State motto of my ancestral homeland, New Hampshire
Do YOU Yahoo!?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Problems with source_rc_confs
On 2 Jun, Sheldon Hearn wrote:
>> At the moment my /etc/rc contains:
>> ---snip---
>> # If there is a global system configuration file, suck it in.
>> #
>> if [ -r /etc/defaults/rc.conf ]; then
>> . /etc/defaults/rc.conf
>> . /etc/rc.conf
>> . /etc/rc.conf.local
>> #source_rc_confs
>> elif [ -r /etc/rc.conf ]; then
>> . /etc/rc.conf
>> fi
>
> Can't you just leave the files alone? rc.i386 doesn't need to
> source_rc_confs, because rc alrady does that:
>
> # If there is a global system configuration file, suck it in.
> #
> if [ -r /etc/defaults/rc.conf ]; then
> . /etc/defaults/rc.conf
> source_rc_confs
> elif [ -r /etc/rc.conf ]; then
> . /etc/rc.conf
> fi
I know, but I had to modify them to get it running.
> Try it with completely unmodified files. It's working for at least 3 of
> us. :-)
I tried it with completely unmodified files just bevore my first mail to
be sure it still didn't work.
I have the output of /etc/rc with "set -x" added to it, do you want it
(together with rc.conf{,.local}) in a private mail (limited to 22k, my
console hadn't more in the scrollback buffer)?
Bye,
Alexander.
--
Failure is not an option. It comes bundled with your Microsoft product.
http://www.Leidinger.net Alexander+Home @ Leidinger.net
GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Problems with source_rc_confs
On Fri, 02 Jun 2000 12:07:13 +0200, Alexander Leidinger wrote: > At the moment my /etc/rc contains: > ---snip--- > # If there is a global system configuration file, suck it in. > # > if [ -r /etc/defaults/rc.conf ]; then > . /etc/defaults/rc.conf > . /etc/rc.conf > . /etc/rc.conf.local > #source_rc_confs > elif [ -r /etc/rc.conf ]; then > . /etc/rc.conf > fi Can't you just leave the files alone? rc.i386 doesn't need to source_rc_confs, because rc alrady does that: # If there is a global system configuration file, suck it in. # if [ -r /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf source_rc_confs elif [ -r /etc/rc.conf ]; then . /etc/rc.conf fi Try it with completely unmodified files. It's working for at least 3 of us. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with source_rc_confs
On 2 Jun, Sheldon Hearn wrote:
>> after the update of my rc scripts (~a month ago if I remember correctly)
>> to use source_rc_conf it didn't boots as expected. E.g. it didn't starts
>> anything from rc.i386. I had to source rc.conf* manually in rc.i386.
>
> Could you run mergemaster again to make sure you didn't botch it last
> time?
I did this a couple of times. I even did a "mergemaster -s".
> Currently, /etc/rc pulls in rc.conf variables with source_rc_confs just
> after checking for a diskless environment, i.e. before doing anything
> else. The variables sourced should exist in the environment of the
> sourced shell scripts as well.
At the moment my /etc/rc contains:
---snip---
# If there is a global system configuration file, suck it in.
#
if [ -r /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
. /etc/rc.conf
. /etc/rc.conf.local
#source_rc_confs
elif [ -r /etc/rc.conf ]; then
. /etc/rc.conf
fi
---snip---
and rc.i386:
---snip--
#!/bin/sh -
#
# $FreeBSD: src/etc/etc.i386/rc.i386,v 1.51 2000/01/24 15:21:43 asmodai Exp $
# Do i386 specific processing
#
. /etc/defaults/rc.conf
. /etc/rc.conf
. /etc/rc.conf.local
---snip---
and defaults/rc.conf:
---snip---
##
### Define source_rc_confs, the mechanism used by /etc/rc.* ##
### scripts to source rc_conf_files overrides safely. ##
##
if [ -z "${source_rc_confs_defined}" ]; then
source_rc_confs_defined=yes
source_rc_confs ( ) {
local i sourced_files
for i in ${rc_conf_files}; do
case ${sourced_files} in
*:$i:*)
;;
*)
sourced_files="${sourced_files}:$i:"
if [ -r $i ]; then
. $i
fi
;;
esac
done
}
fi
---snip---
Bye,
Alexander.
--
Weird enough for government work.
http://www.Leidinger.net Alexander+Home @ Leidinger.net
GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Problems with source_rc_confs
On Fri, 02 Jun 2000 09:46:04 +0200, Alexander Leidinger wrote: > after the update of my rc scripts (~a month ago if I remember correctly) > to use source_rc_conf it didn't boots as expected. E.g. it didn't starts > anything from rc.i386. I had to source rc.conf* manually in rc.i386. Could you run mergemaster again to make sure you didn't botch it last time? Currently, /etc/rc pulls in rc.conf variables with source_rc_confs just after checking for a diskless environment, i.e. before doing anything else. The variables sourced should exist in the environment of the sourced shell scripts as well. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
