On Wed, Oct 30, 2002 at 02:36:01PM -0800, Bill Fenner wrote: [ snip ] > > The update to the /etc/rc.d infrastructure keeps the ability to run > twice, but does not actually run it twice. I started creating an > /etc/rc.d/sysctl-last that would run "/etc/rc.d/sysctl lastload", > but realized that I didn't know how to say where the first/second > call should go. To strictly follow /etc/rc.d, I could change the > existing /etc/rc.d/sysctl to say "BEFORE: serial" and add "BEFORE: > securelevel" to sysctl-last, but I'm not sure this is appropriate given > the meta-checkpoints that we have.
One of the hard things while I was doing the porting was deciding whether something in /etc/rc was there because it *must* run before the commands that were after it and after the commands that came before it. Since there haven't been any complaints in that regard I don't think the current order has broken anything. The general rule is to put something in REQUIRE and/or BEFORE only if it is necessary that some script be run before or after the current script. So, if the sysctls *must* be set before SERIAL, it should be in the BEFORE line. Otherwise, I would leave it as is and run `/etc/rc.d/sysctl lastload' in /etc/rc.d/securelevel just before rasing the securelevel (Please see the attached patch). > > (It also raises the question of if /etc/rc.d/securelevel actually > runs at the right time. /etc/rc puts it almost at the absolute end, > while rcorder sticks it somewhere in the middle -- number 67 of 102 > on my system.) We wanted to keep the differences between our scripts and NetBSD's to a minimum. So, if it turns out we've broken something because of where rcorder puts the securelevel script, then we'll have to modify the BEFORE line of the affected script. Cheers, Mike -- GPG Key: http://www.identd.net/~mtm/gpg.key pub 1024D/7D39509A 2002-10-08 Mike Makonnen <[EMAIL PROTECTED]> Key fingerprint = 5491 488A 0445 2DCC 777B 1F03 F3AB F9F8 7D39 509A
msg46410/pgp00000.pgp
Description: PGP signature
