Re: HEADS UP: MFC of local_startup changes to rc.d complete
El Lunes, 26 de Diciembre de 2005 09:53, Doug Barton escribió: Jose M Rodriguez wrote: But this doesn't solve the real problem. We've lost a reference model about rc and the interaction with the base system and ports. I'm not sure what that last sentence means. Form our old rc system, to the initial import from NetBSD, to what we have now in HEAD. A lot of things has been changed, an now, it's really hard to get an idea about the boot process and the order used to launch the components. - some kinda of style for ports/system rc scripts - some docs about keywords and stage support As I said in one of my recent heads up messages, man rc(8). As far I know, rc(8) depends on the FreeBSD version used. I doubt RELENG_4_11 rc(8) may be enough. This kind of information must be on the porter's handbook. - some kinda of timeline model Timeline for what? To guess the keywords to use for the rc script. -- josemi -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
Em Qui, 2005-12-29 às 16:41 +0100, Jose M Rodriguez escreveu: A lot of things has been changed, an now, it's really hard to get an idea about the boot process and the order used to launch the components. I'm sorry if I am saying something that is out of the discussion, I didn't see the first messages, but Isn't it easy to do something like: # cd /etc/rc.d # rcorder * preseedrandom initdiskless rcconf.sh initrandom dumpon vinum gbde_swap gbde ccd (supressed output) -- Carlos E. G. Carvalho OpenIT Solucoes Tecnologicas Consultor Unix/Internet Tel. +55 21 2508-9103 http://www.OpenIT.com.br http://www.MyFreeBSD.com.br signature.asc Description: This is a digitally signed message part
Re: HEADS UP: MFC of local_startup changes to rc.d complete
El Jueves, 29 de Diciembre de 2005 16:54, Carlos Eduardo G. Carvalho escribió: Em Qui, 2005-12-29 às 16:41 +0100, Jose M Rodriguez escreveu: A lot of things has been changed, an now, it's really hard to get an idea about the boot process and the order used to launch the components. I'm sorry if I am saying something that is out of the discussion, I didn't see the first messages, but Isn't it easy to do something like: # cd /etc/rc.d # rcorder * preseedrandom initdiskless rcconf.sh initrandom dumpon vinum gbde_swap gbde ccd (supressed output) Which only covers the base system scripts and send you docens of entries Also, now in head, a second scan is done. As far I know, the most important point are: mountcritlocal NETWORKING mountcritremote SERVERS DAEMON LOGIN I never said that this info is not guessable or even documented. Only that: - The docs are disperse. - The docs are not porters aware -- josemi -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
Jose M Rodriguez wrote: El Lunes, 26 de Diciembre de 2005 09:53, Doug Barton escribió: Jose M Rodriguez wrote: But this doesn't solve the real problem. We've lost a reference model about rc and the interaction with the base system and ports. I'm not sure what that last sentence means. Form our old rc system, to the initial import from NetBSD, to what we have now in HEAD. Well, if you think it's important, please feel free to write this up and submit it. I'm not sure what value it would have. A lot of things has been changed, an now, it's really hard to get an idea about the boot process and the order used to launch the components. See below. - some kinda of style for ports/system rc scripts - some docs about keywords and stage support As I said in one of my recent heads up messages, man rc(8). As far I know, rc(8) depends on the FreeBSD version used. Yes, of course. So for any given system, you have an approximation of what you are looking for. I doubt RELENG_4_11 rc(8) may be enough. This kind of information must be on the porter's handbook. Feel free to submit these patches as well. Also, since this new facility is not going to be MFC'ed past RELENG_6, changing the REQUIRE lines in the scripts won't have any effect on earlier systems. - some kinda of timeline model Timeline for what? To guess the keywords to use for the rc script. Ah, got it. You can get a good start on that by doing: rcorder -s nostart /etc/rc.d/* Once we get a better handle on where the key points for ports are, we'll add something to rc(8). Right now, it looks like anything that is going to run as part of the system it should REQUIRE: DAEMON, if it is something that is going to start as a user, it should REQUIRE: LOGIN. hth, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On 21/12/2005, at 7:23 PM, Doug Barton wrote: As has been discussed for a couple weeks now, I have MFC'ed to RELENG_6 the changes in /etc/rc* that bring new-style boot scripts from the local_startup directories (by default /usr/local/etc/rc.d and /usr/X11R6/etc/rc.d) into the base rcorder. How does this correlate with the planned implementation of launchd in FreeBSD? http://wikitest.freebsd.org/moin.cgi/launchd Perhaps it is too early for you to say, but it would seem that launchd is a much more sophisticated system that would bring a whole range of benefits to FreeBSD. Is work still progressing on that? Will these changes to /etc/rc allow for a migration path? Cheers Ari Maniatis -- ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
Jose M Rodriguez wrote: But this doesn't solve the real problem. We've lost a reference model about rc and the interaction with the base system and ports. I'm not sure what that last sentence means. - some kinda of style for ports/system rc scripts - some docs about keywords and stage support As I said in one of my recent heads up messages, man rc(8). - some kinda of timeline model Timeline for what? -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
Florent Thoumie wrote:
rcNG was the word for using rc.subr.
rcNG stands for rc Next Generation. It's not the next generation anymore.
Using the .sh extension prevents from conflicts in ${WRKDIR} and you know
what kind of file it is in ${FILESDIR}. Anyway, what is the difference
between adding .sh suffix in some cases and removing it in some cases ?
As I mentioned in one of my messages, we can easily fix this by changing
bsd.port.mk to take file.in and output $WRKDIR/file.out. I haven't finished
the patch to bsd.port.mk yet, but it's a trivial change.
Doug
--
This .signature sanitized for your protection
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
El Miércoles, 21 de Diciembre de 2005 09:23, Doug Barton escribió: Howdy, As has been discussed for a couple weeks now, I have MFC'ed to RELENG_6 the changes in /etc/rc* that bring new-style boot scripts from the local_startup directories (by default /usr/local/etc/rc.d and /usr/X11R6/etc/rc.d) into the base rcorder. For old style scripts (those that don't use rc.subr) there should be no changes. They will still run out of /etc/rc.d/localpkg. For those scripts that have been converted to use rc.subr, they will still be run the same way that they are now. The difference is that they will be added to the base rcorder list, and run in that spot instead of in localpkg. To get an idea of the current list (minus any local scripts) in RELENG_6, see http://people.freebsd.org/~dougb/rcorder-6.all In an ideal world, there should be no problems related to running the scripts in a different order. However, it is anticipated that there may be a brief period while scripts for whom the ordering is significant are adjusted. These are extremely easy changes to make, and do not otherwise affect the functionality of the packages in any way. If you run into one of these problems, please report it to the port's maintainer, and [EMAIL PROTECTED] ASAP. In almost all cases however the scripts will run close enough to their old position as not to make any difference, since currently localpkg is fairly late in the order. This change is being made so that port authors and users can take advantage of the greater control these features will give them. Some authors have already stepped forward and added new functionality to their ports that take advantage of these features. If anyone has questions about the changes, or what they offer you, feel free to ask on [EMAIL PROTECTED] You can also find more information in rc(8) on an updated system. Happy Holidays, Doug I'm not sure this is the way to go, but ... Can someone put a document on what is the desired model? I think we have too much little pieces of disperse notes about this. Also, some working notes about ports and RELENG_4/RELENG_5 src issues will be of interest. Hope this can be tweak in time for 6.1 (Jan). -- josemi -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Friday 23 December 2005 15:19, Jose M Rodriguez wrote: I'm not sure this is the way to go, but ... Can someone put a document on what is the desired model? I think we have too much little pieces of disperse notes about this. Also, some working notes about ports and RELENG_4/RELENG_5 src issues will be of interest. Hope this can be tweak in time for 6.1 (Jan). Convert your old script to rcNG scripts and use USE_RC_SUBR= script.sh. Ensure that the rcorder preamble contains meaningful keywords (PROVIDES, REQUIRES, BEFORE, ...) for all your rcNG scripts. bsd.port.mk should do the rest. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer pgpiY2qd3eeZG.pgp Description: PGP signature
Re: HEADS UP: MFC of local_startup changes to rc.d complete
El Viernes, 23 de Diciembre de 2005 15:38, Florent Thoumie escribió: On Friday 23 December 2005 15:19, Jose M Rodriguez wrote: I'm not sure this is the way to go, but ... Can someone put a document on what is the desired model? I think we have too much little pieces of disperse notes about this. Also, some working notes about ports and RELENG_4/RELENG_5 src issues will be of interest. Hope this can be tweak in time for 6.1 (Jan). Convert your old script to rcNG scripts and use USE_RC_SUBR= script.sh. Ensure that the rcorder preamble contains meaningful keywords (PROVIDES, REQUIRES, BEFORE, ...) for all your rcNG scripts. bsd.port.mk should do the rest. Some time working with binary oriented software systems have teach me that simple changes may become harder when size and numbers grow up. I think this may be even harder with a non-binary oriented system like ports. But this doesn't solve the real problem. We've lost a reference model about rc and the interaction with the base system and ports. - some kinda of style for ports/system rc scripts - some docs about keywords and stage support - some kinda of timeline model ... I think that this is more or less out there, but not in a strict document that may guide for the change to FreeBSD-6.1 -- josemi -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Friday 23 December 2005 16:12, Jose M Rodriguez wrote: El Viernes, 23 de Diciembre de 2005 15:38, Florent Thoumie escribió: On Friday 23 December 2005 15:19, Jose M Rodriguez wrote: I'm not sure this is the way to go, but ... Can someone put a document on what is the desired model? I think we have too much little pieces of disperse notes about this. Also, some working notes about ports and RELENG_4/RELENG_5 src issues will be of interest. Hope this can be tweak in time for 6.1 (Jan). Convert your old script to rcNG scripts and use USE_RC_SUBR= script.sh. Ensure that the rcorder preamble contains meaningful keywords (PROVIDES, REQUIRES, BEFORE, ...) for all your rcNG scripts. bsd.port.mk should do the rest. Some time working with binary oriented software systems have teach me that simple changes may become harder when size and numbers grow up. I think this may be even harder with a non-binary oriented system like ports. But this doesn't solve the real problem. We've lost a reference model about rc and the interaction with the base system and ports. - some kinda of style for ports/system rc scripts ? - some docs about keywords and stage support It's quite simple enough but yar wrote an article about it : http://people.freebsd.org/~yar/rcng/article.html I thought it already made it to the doc tree. - some kinda of timeline model There's one. Commit, MFC, fix broken ports. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer pgp1HMFMmWWyU.pgp Description: PGP signature
Re: HEADS UP: MFC of local_startup changes to rc.d complete
El Viernes, 23 de Diciembre de 2005 16:17, Florent Thoumie escribió: On Friday 23 December 2005 16:12, Jose M Rodriguez wrote: El Viernes, 23 de Diciembre de 2005 15:38, Florent Thoumie escribió: On Friday 23 December 2005 15:19, Jose M Rodriguez wrote: I'm not sure this is the way to go, but ... snip/ - some kinda of style for ports/system rc scripts ? In the way of style(9). - some docs about keywords and stage support It's quite simple enough but yar wrote an article about it : http://people.freebsd.org/~yar/rcng/article.html I thought it already made it to the doc tree. I think this is about the rc framework. But not about the hard details: Also, if we now support rcorder for localpkg, we're implemening, at last, a two stage boot process ( we can't read the local rc scripts at the very beginning of the boot process). - some kinda of timeline model There's one. Commit, MFC, fix broken ports. Sorry, it's boot process timeline, not working timeline. We need a good reference for good tagging of rc scripts. -- josemi -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Fri, 23 Dec 2005 15:38:15 +0100
Florent Thoumie [EMAIL PROTECTED] wrote:
On Friday 23 December 2005 15:19, Jose M Rodriguez wrote:
I'm not sure this is the way to go, but ...
Can someone put a document on what is the desired model? I think we
have too much little pieces of disperse notes about this.
Also, some working notes about ports and RELENG_4/RELENG_5 src
issues will be of interest.
Hope this can be tweak in time for 6.1 (Jan).
Convert your old script to rcNG scripts and use USE_RC_SUBR=
script.sh. Ensure that the rcorder preamble contains meaningful
keywords (PROVIDES, REQUIRES, BEFORE, ...) for all your rcNG scripts.
bsd.port.mk should do the rest.
You should actually convert your old script to a ``rc.d'' script,
that's how they are called now.
Also, if your script is rc.d compatible you should use:
USE_RC_SUBR=script (without .sh)
For now it doesn't matter because bsd.port.mk install all USE_RC_SUBR
scripts with .sh extension, but see below
On Thu, 22 Dec 2005 10:52:27 -0800
Brooks Davis [EMAIL PROTECTED] wrote:
[ ... ]
Does this mean that we will remove the .sh extension on port rc.d
startup scripts? Because a) it's been only running .sh scripts for
quite a while, and b) it's really nice and easy to disable scripts
by moving them to .old or another extension..
Yes. You should be able to disable any correctly written rc.d script
by setting the variable listed by running script rcvar to NO in
/etc/rc.conf (and this should be the default). In 8.0 any scripts
ending in .sh will be run in the context of /etc/rc so they should be
extremely rare and must be very carefully crafted to avoid namespace
pollution.
Also, how will this effect cups which installs a .sample file? and
any other port that does this?
.sample files should go away. If for some reason a script must
be modified to be useful, the sample version should go under
${PREFIX}/share.
--
IOnut - Unregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
root rot
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Friday 23 December 2005 18:52, Ion-Mihai Tetcu wrote:
On Fri, 23 Dec 2005 15:38:15 +0100
Florent Thoumie [EMAIL PROTECTED] wrote:
On Friday 23 December 2005 15:19, Jose M Rodriguez wrote:
I'm not sure this is the way to go, but ...
Can someone put a document on what is the desired model? I think we
have too much little pieces of disperse notes about this.
Also, some working notes about ports and RELENG_4/RELENG_5 src
issues will be of interest.
Hope this can be tweak in time for 6.1 (Jan).
Convert your old script to rcNG scripts and use USE_RC_SUBR=
script.sh. Ensure that the rcorder preamble contains meaningful
keywords (PROVIDES, REQUIRES, BEFORE, ...) for all your rcNG scripts.
bsd.port.mk should do the rest.
You should actually convert your old script to a ``rc.d'' script,
that's how they are called now.
rcNG was the word for using rc.subr. From the beginning these
rc.subr-powered scripts have been using the rcorder preamble and have
always been rc.d script actually. Since we're talking about the same
thing,
I'm not sure words are really important.
Also, if your script is rc.d compatible you should use:
USE_RC_SUBR=script (without .sh)
For now it doesn't matter because bsd.port.mk install all USE_RC_SUBR
scripts with .sh extension, but see below
Using the .sh extension prevents from conflicts in ${WRKDIR} and you
know
what kind of file it is in ${FILESDIR}. Anyway, what is the difference
between adding .sh suffix in some cases and removing it in some cases ?
--
Florent Thoumie
[EMAIL PROTECTED]
FreeBSD Committer
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Fri, 23 Dec 2005 19:28:19 +0100
Florent Thoumie [EMAIL PROTECTED] wrote:
On Friday 23 December 2005 18:52, Ion-Mihai Tetcu wrote:
On Fri, 23 Dec 2005 15:38:15 +0100
Florent Thoumie [EMAIL PROTECTED] wrote:
On Friday 23 December 2005 15:19, Jose M Rodriguez wrote:
I'm not sure this is the way to go, but ...
Can someone put a document on what is the desired model? I
think we have too much little pieces of disperse notes about
this.
Also, some working notes about ports and RELENG_4/RELENG_5 src
issues will be of interest.
Hope this can be tweak in time for 6.1 (Jan).
Convert your old script to rcNG scripts and use
USE_RC_SUBR= script.sh. Ensure that the rcorder preamble contains
meaningful keywords (PROVIDES, REQUIRES, BEFORE, ...) for all
your rcNG scripts. bsd.port.mk should do the rest.
You should actually convert your old script to a ``rc.d'' script,
that's how they are called now.
rcNG was the word for using rc.subr. From the beginning
these rc.subr-powered scripts have been using the rcorder preamble
and have always been rc.d script actually. Since we're talking about
the same thing, I'm not sure words are really important.
Well, I was corrected by dougb@
For me a rc.d script is one that on:
1. has the right keywords, ... (ie. is rcNG)
2. has the right extension depending if it must be sourced or not
(on a a system which has local_startup scripts in the base rcorder -
HEAD and 6-STABLE for now).
Also, if your script is rc.d compatible you should use:
USE_RC_SUBR=script (without .sh)
For now it doesn't matter because bsd.port.mk install all
USE_RC_SUBR scripts with .sh extension, but see below
Using the .sh extension prevents from conflicts in ${WRKDIR}
This is indeed a problem; perhaps we should hack bsd.port.mk to avoid
this.
and you know what kind of file it is in ${FILESDIR}. Anyway, what is
This is easy to fix, no ?
the difference between adding .sh suffix in some cases and removing
it in some cases ?
If you are asking what is the difference between how it is/will be treated by
rc.subr the answer is in the quote from Brooks which you removed.
An interesting discussion is in
http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/90070 and a solution is
tested (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/90150).
I think naming a script without .sh make it easy to see it's rc.d ready.
--
IOnut - Unregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
BOFH excuse #386:
The Internet is being scanned for viruses
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
Greg Rivers wrote: On Wed, 21 Dec 2005, Doug Barton wrote: As has been discussed for a couple weeks now, I have MFC'ed to RELENG_6 the changes in /etc/rc* that bring new-style boot scripts from the local_startup directories (by default /usr/local/etc/rc.d and /usr/X11R6/etc/rc.d) into the base rcorder... This seems to have broken ppp-user for me. Apparently the ppp arguments are being executed without the ppp command: This is fixed now, thanks; and sorry for the hassle. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADS UP: MFC of local_startup changes to rc.d complete
Howdy, As has been discussed for a couple weeks now, I have MFC'ed to RELENG_6 the changes in /etc/rc* that bring new-style boot scripts from the local_startup directories (by default /usr/local/etc/rc.d and /usr/X11R6/etc/rc.d) into the base rcorder. For old style scripts (those that don't use rc.subr) there should be no changes. They will still run out of /etc/rc.d/localpkg. For those scripts that have been converted to use rc.subr, they will still be run the same way that they are now. The difference is that they will be added to the base rcorder list, and run in that spot instead of in localpkg. To get an idea of the current list (minus any local scripts) in RELENG_6, see http://people.freebsd.org/~dougb/rcorder-6.all In an ideal world, there should be no problems related to running the scripts in a different order. However, it is anticipated that there may be a brief period while scripts for whom the ordering is significant are adjusted. These are extremely easy changes to make, and do not otherwise affect the functionality of the packages in any way. If you run into one of these problems, please report it to the port's maintainer, and [EMAIL PROTECTED] ASAP. In almost all cases however the scripts will run close enough to their old position as not to make any difference, since currently localpkg is fairly late in the order. This change is being made so that port authors and users can take advantage of the greater control these features will give them. Some authors have already stepped forward and added new functionality to their ports that take advantage of these features. If anyone has questions about the changes, or what they offer you, feel free to ask on [EMAIL PROTECTED] You can also find more information in rc(8) on an updated system. Happy Holidays, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Wed, Dec 21, 2005 at 12:23:20AM -0800, Doug Barton wrote: If you run into one of these problems, please report it to the port's maintainer, and [EMAIL PROTECTED] ASAP. ITYM [EMAIL PROTECTED] mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
Mark Linimon wrote: On Wed, Dec 21, 2005 at 12:23:20AM -0800, Doug Barton wrote: If you run into one of these problems, please report it to the port's maintainer, and [EMAIL PROTECTED] ASAP. ITYM [EMAIL PROTECTED] Yep, sorry. :) -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Wed, 21 Dec 2005, Doug Barton wrote: As has been discussed for a couple weeks now, I have MFC'ed to RELENG_6 the changes in /etc/rc* that bring new-style boot scripts from the local_startup directories (by default /usr/local/etc/rc.d and /usr/X11R6/etc/rc.d) into the base rcorder... This seems to have broken ppp-user for me. Apparently the ppp arguments are being executed without the ppp command: + su -m vpn -c sh -c -quiet -ddial vpn-tcp -quiet: not found Otherwise, everything seems to be working fine. See a trace of `ppp-user start' below. -- Greg # /bin/sh -x /etc/rc.d/ppp-user start + . /etc/rc.subr + [ -z ] + _rc_subr_loaded=YES + SYSCTL=/sbin/sysctl + SYSCTL_N=/sbin/sysctl -n + CMD_OSTYPE=/sbin/sysctl -n kern.ostype + /sbin/sysctl -n kern.ostype + OSTYPE=FreeBSD + ID=/usr/bin/id + IDCMD=if [ -x /usr/bin/id ]; then /usr/bin/id -un; fi + SYSCTL_W=/sbin/sysctl + name=ppp + set_rcvar + [ -z ] + base_var=ppp + echo ppp_enable + rcvar=ppp_enable + start_precmd=ppp_precmd + start_postcmd=ppp_postcmd + load_rc_config ppp + _command=ppp + [ -z ppp ] + false + [ -r /etc/defaults/rc.conf ] + debug Sourcing /etc/defaults/rc.conf + . /etc/defaults/rc.conf + rc_debug=NO + rc_info=NO + rcshutdown_timeout=30 + early_late_divider=mountcritlocal + swapfile=NO + apm_enable=NO + apmd_enable=NO + apmd_flags= + devd_enable=YES + devd_flags= + kldxref_enable=NO + kldxref_clobber=NO + kldxref_module_path= + pccard_enable=NO + pccard_mem=DEFAULT + pccard_beep=2 + pccard_ifconfig=NO + pccardd_flags=-z + pccard_conf=/etc/defaults/pccard.conf + powerd_enable=NO + powerd_flags= + removable_route_flush=YES + tmpmfs=AUTO + tmpsize=20m + tmpmfs_flags=-S -M + varmfs=AUTO + varsize=32m + varmfs_flags=-S -M + populate_var=AUTO + local_startup=/usr/local/etc/rc.d /usr/X11R6/etc/rc.d + script_name_sep= + rc_conf_files=/etc/rc.conf /etc/rc.conf.local + gbde_autoattach_all=NO + gbde_devices=NO + gbde_attach_attempts=3 + gbde_lockdir=/etc + geli_devices= + geli_tries= + geli_default_flags= + geli_autodetach=YES + geli_swap_flags=-a aes -l 256 -s 4096 -d + root_rw_mount=YES + fsck_y_enable=NO + background_fsck=YES + background_fsck_delay=60 + netfs_types=nfs:NFS nfs4:NFS4 smbfs:SMB portalfs:PORTAL nwfs:NWFS + extra_netfs_types=NO + hostname= + nisdomainname=NO + dhclient_program=/sbin/dhclient + dhclient_flags= + background_dhclient=NO + firewall_enable=NO + firewall_script=/etc/rc.firewall + firewall_type=UNKNOWN + firewall_quiet=NO + firewall_logging=NO + firewall_flags= + ip_portrange_first=NO + ip_portrange_last=NO + ike_enable=NO + ike_program=/usr/local/sbin/isakmpd + ike_flags= + ipsec_enable=NO + ipsec_file=/etc/ipsec.conf + natd_program=/sbin/natd + natd_enable=NO + natd_interface= + natd_flags= + ipfilter_enable=NO + ipfilter_program=/sbin/ipf + ipfilter_rules=/etc/ipf.rules + ipfilter_flags= + ipnat_enable=NO + ipnat_program=/sbin/ipnat + ipnat_rules=/etc/ipnat.rules + ipnat_flags= + ipmon_enable=NO + ipmon_program=/sbin/ipmon + ipmon_flags=-Ds + ipfs_enable=NO + ipfs_program=/sbin/ipfs + ipfs_flags= + pf_enable=NO + pf_rules=/etc/pf.conf + pf_program=/sbin/pfctl + pf_flags= + pflog_enable=NO + pflog_logfile=/var/log/pflog + pflog_program=/sbin/pflogd + pflog_flags= + pfsync_enable=NO + pfsync_syncdev= + pfsync_ifconfig= + tcp_extensions=YES + log_in_vain=0 + tcp_keepalive=YES + tcp_drop_synfin=NO + icmp_drop_redirect=NO + icmp_log_redirect=NO + network_interfaces=auto + cloned_interfaces= + ifconfig_lo0=inet 127.0.0.1 + sppp_interfaces= + gif_interfaces=NO + ppp_enable=NO + ppp_program=/usr/sbin/ppp + ppp_mode=auto + ppp_nat=YES + ppp_profile=papchap + ppp_user=root + syslogd_enable=YES + syslogd_program=/usr/sbin/syslogd + syslogd_flags=-s + inetd_enable=NO + inetd_program=/usr/sbin/inetd + inetd_flags=-wW -C 60 + named_enable=NO + named_program=/usr/sbin/named + named_flags=-u bind + named_pidfile=/var/run/named/pid + named_chrootdir=/var/named + named_chroot_autoupdate=YES + named_symlink_enable=YES + kerberos5_server_enable=NO + kerberos5_server=/usr/libexec/kdc + kerberos5_server_flags= + kadmind5_server_enable=NO + kadmind5_server=/usr/libexec/kadmind + kpasswdd_server_enable=NO + kpasswdd_server=/usr/libexec/kpasswdd + rwhod_enable=NO + rwhod_flags= + rarpd_enable=NO + rarpd_flags= + bootparamd_enable=NO + bootparamd_flags= + pppoed_enable=NO + pppoed_provider=* + pppoed_flags=-P /var/run/pppoed.pid + pppoed_interface=fxp0 + sshd_enable=NO + sshd_program=/usr/sbin/sshd + sshd_flags= + amd_enable=NO + amd_flags=-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map + amd_map_program=NO + nfs_client_enable=NO + nfs_access_cache=2 + nfs_server_enable=NO + nfs_server_flags=-u -t -n 4 + mountd_enable=NO + mountd_flags=-r + weak_mountd_authentication=NO + nfs_reserved_port_only=NO + nfs_bufpackets= + rpc_lockd_enable=NO + rpc_statd_enable=NO + rpcbind_enable=NO + rpcbind_program=/usr/sbin/rpcbind + rpcbind_flags= + rpc_ypupdated_enable=NO + keyserv_enable=NO + keyserv_flags= +
