Re: rc_ng breakage introduced with src/etc/rc.d/Makefile 1.5
On Wed, 27 Nov 2002, Mike Makonnen wrote: On Thu, Nov 28, 2002 at 01:31:26AM +0300, Sergey Mokryshev wrote: [ snip ] ldconfig does not have proper anchor and is mistakenly ordered to run first (without any filesystems mounted (except R/O root) yet). This is a good example of why I didn't support the removal of the NetBSD scripts when it was done. However, I can also understand Gordon't point of view and why he removed them: namely, because of rc.d bloat, confusing users, and the implied suggestion that we support those scripts on our platform (correct me if I'm wrong Gordon). * So I'm complaining mostly about removing files without fixing dependencies in the remaining scripts * Probably the best solution is to backout rev 1.5 of src/etc/rc.d/Makefile. It was tested before 5.0-DP2 and it just works. The dependencies are fine for the default order. I don't think there was any implicit or explicit guarantee that if you changed the order things wouldn't break. For your particular situation I think the following will give the desired order: 1. Leave rc.d/named alone 2. Modify rc.d/ldconfig : # REQUIRE: SERVERS # BEFORE: named Mike, I have no problem myself, I've already done this (a similar one) change. (Anyway, thank you :-) ) I'm keeping in mind new users and upgrades from FreeBSD4 when 5.0 become -RELEASE and -STABLE? The rc_ng scripts is left in useful, but unstable state, there are many possibilities that someone will hit the same problem. May be we should put some of the scripts back? At least I'd prefer to put back every script with a cross-reference. The other solution is to rework every rc.d script and change references of the missing ones. Leaving scripts the way it is now is not a good thing (Just a MHO). Sincerely yours, Sergey Mokryshev. -- Sergey S. Mokryshev [EMAIL PROTECTED] SMP453, MOKR-RIPN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: rc_ng breakage introduced with src/etc/rc.d/Makefile 1.5
On Wed, Nov 27, 2002 at 02:08:40AM +0300, Sergey Mokryshev wrote: Yes, I don't see these errors. But some scripts can change execution order without anchors like mountall For example, adding ldconfig dependancy directly into named brings this order: root@girvas-gw:/etc/rc.d# rcorder -k FreeBSD -s nostart * 2/dev/null ldconfig initdiskless initrandom dumpon vinum Isn't this wrong? I'm not in front of a -current box right now so I can't test it, but generally if you change the default order of the scripts you _may_ need to modify one or more BEFORE or REQUIRE lines. That's what they are there for after all. Cheers. -- Mike Makonnen [EMAIL PROTECTED] GPG Key-ID: 0xDBCC68B9 GPG-KEY: http://www.identd.net/~mtm/mtm.asc Key fingerprint = D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 msg47596/pgp0.pgp Description: PGP signature
Re: rc_ng breakage introduced with src/etc/rc.d/Makefile 1.5
On Wed, 27 Nov 2002, Mike Makonnen wrote: On Wed, Nov 27, 2002 at 02:08:40AM +0300, Sergey Mokryshev wrote: Yes, I don't see these errors. But some scripts can change execution order without anchors like mountall For example, adding ldconfig dependancy directly into named brings this order: root@girvas-gw:/etc/rc.d# rcorder -k FreeBSD -s nostart * 2/dev/null ldconfig initdiskless initrandom dumpon vinum Isn't this wrong? I'm not in front of a -current box right now so I can't test it, but generally if you change the default order of the scripts you _may_ need to modify one or more BEFORE or REQUIRE lines. That's what they are there for after all. Dear Mike, here are two scenarios, one with 'mountall' installed and another one without. I've changed named at first (remember, the problem which lead me to dig /etc/rc.d futher was missing /usr/local/lib in linker hints at the time of named load) # diff -du /etc/rc.d/named.orig /etc/rc.d/named --- /etc/rc.d/named.origThu Nov 28 01:06:18 2002 +++ /etc/rc.d/named Thu Nov 28 01:06:26 2002 @@ -5,7 +5,7 @@ # # PROVIDE: named -# REQUIRE: SERVERS +# REQUIRE: SERVERS ldconfig # BEFORE: DAEMON # KEYWORD: FreeBSD NetBSD -- With 'mountall' and other old scripts: root@amber:/etc/rc.d# rcorder -k FreeBSD -s nostart * 2/dev/null initdiskless initrandom dumpon vinum ccd swap1 fsck root mountcritlocal diskless addswap ttys ipsec ipfilter sysctl random adjkerntz atm1 cleanvar sppp serial pccard network1 ppp-user ipfw atm2.sh network2 ip6fw network_ipv6 NETWORKING mountcritremote lomac syslogd ldconfig ipmon isdnd savecore SERVERS named ldconfig gets proper anchoring and seems to be placed in the right place (all filesystems should be mounted at this point) - This is from the fresh installation. rc.d/mountd is modified as shown above, no other changes in /etc/rc.d/* was made. root@girvas-gw:/etc/rc.d# rcorder -k FreeBSD -s nostart * 2/dev/null ldconfig initdiskless initrandom dumpon vinum ccd swap1 ldconfig does not have proper anchor and is mistakenly ordered to run first (without any filesystems mounted (except R/O root) yet). * So I'm complaining mostly about removing files without fixing dependencies in the remaining scripts * Unfortunately I don't have time now to dig in and make patches. Also FreeBSD is in code freeze and I don't think that there is time left to properly check system startup in all scenarios (seems to dangerous to me). Probably the best solution is to backout rev 1.5 of src/etc/rc.d/Makefile. It was tested before 5.0-DP2 and it just works. Sincerely yours, Sergey Mokryshev. -- Sergey S. Mokryshev [EMAIL PROTECTED] SMP453, MOKR-RIPN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: rc_ng breakage introduced with src/etc/rc.d/Makefile 1.5
On Thu, Nov 28, 2002 at 01:31:26AM +0300, Sergey Mokryshev wrote: [ snip ] ldconfig does not have proper anchor and is mistakenly ordered to run first (without any filesystems mounted (except R/O root) yet). This is a good example of why I didn't support the removal of the NetBSD scripts when it was done. However, I can also understand Gordon't point of view and why he removed them: namely, because of rc.d bloat, confusing users, and the implied suggestion that we support those scripts on our platform (correct me if I'm wrong Gordon). * So I'm complaining mostly about removing files without fixing dependencies in the remaining scripts * Probably the best solution is to backout rev 1.5 of src/etc/rc.d/Makefile. It was tested before 5.0-DP2 and it just works. The dependencies are fine for the default order. I don't think there was any implicit or explicit guarantee that if you changed the order things wouldn't break. For your particular situation I think the following will give the desired order: 1. Leave rc.d/named alone 2. Modify rc.d/ldconfig : # REQUIRE: SERVERS # BEFORE: named Cheers. -- Mike Makonnen [EMAIL PROTECTED] GPG Key-ID: 0xDBCC68B9 GPG-KEY: http://www.identd.net/~mtm/mtm.asc Key fingerprint = D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 msg47653/pgp0.pgp Description: PGP signature
rc_ng breakage introduced with src/etc/rc.d/Makefile 1.5
Hello. In the revision 1.5 of src/etc/rc.d/Makefile Gordon introduces the following breakage into rc_ng scripts (didn't find it early, because installed boxes works as expected and the bug introduce itself a) only with a new installations; b) when rcorder run manually) root@girvas-gw:/etc/rc.d# rcorder -k FreeBSD -s nostart * /dev/null rcorder: requirement `ppp' in file `rpcbind' has no providers. rcorder: requirement `beforenetlkm' in file `ipsec' has no providers. rcorder: requirement `beforenetlkm' in file `ipfilter' has no providers. rcorder: requirement `altqd' in file `NETWORKING' has no providers. rcorder: requirement `dhclient' in file `NETWORKING' has no providers. rcorder: requirement `network' in file `NETWORKING' has no providers. rcorder: requirement `wscons' in file `syslogd' has no providers. rcorder: requirement `sysdb' in file `syslogd' has no providers. rcorder: requirement `mountall' in file `accounting' has no providers. rcorder: requirement `mountall' in file `amd' has no providers. rcorder: requirement `mountall' in file `cleartmp' has no providers. rcorder: requirement `mountall' in file `ldconfig' has no providers. rcorder: requirement `beforemountlkm' in file `mountd' has no providers. rcorder: requirement `mountall' in file `mountd' has no providers. rcorder: requirement `aftermountlkm' in file `securelevel' has no providers. Another one found - Once you install /usr/ports/net/bind9-dlz WITH_OPENSSL=yes it can not start, because /etc/rc.d/ldconfig seed /var/run/ld-elf.so.hints later and /usr/local/sbin/named depends on the libraries in /usr/local/lib # ldd /usr/local/sbin/named /usr/local/sbin/named: libcrypto.so.3 = /usr/local/lib/libcrypto.so.3 (0x281aa000) libmysqlclient.so.10 = /usr/local/lib/mysql/libmysqlclient.so.10 (0x28272000) libz.so.2 = /usr/lib/libz.so.2 (0x2829) libcrypt.so.2 = /usr/lib/libcrypt.so.2 (0x2829e000) libm.so.2 = /usr/lib/libm.so.2 (0x282b7000) libc_r.so.5 = /usr/lib/libc_r.so.5 (0x282d5000) libc.so.5 = /usr/lib/libc.so.5 (0x282f8000) As a quick fix I've added ldconfig as a dependancy to /etc/rc.d/SERVERS, but I'm not sure if it breaks something in diskless environments. I could not find a PR on this. Should I fill one? Sincerely yours, Sergey Mokryshev. -- Sergey S. Mokryshev [EMAIL PROTECTED] SMP453, MOKR-RIPN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: rc_ng breakage introduced with src/etc/rc.d/Makefile 1.5
These are benign. Those scripts are used by NetBSD only. You don't see the errors on boot because of a 2/dev/null in /etc/rc. Cheers. -- Mike Makonnen [EMAIL PROTECTED] GPG Key-ID: 0xDBCC68B9 GPG-KEY: http://www.identd.net/~mtm/mtm.asc Key fingerprint = D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 msg47550/pgp0.pgp Description: PGP signature
Re: rc_ng breakage introduced with src/etc/rc.d/Makefile 1.5
On Tue, 26 Nov 2002, Mike Makonnen wrote: These are benign. Those scripts are used by NetBSD only. You don't see the errors on boot because of a 2/dev/null in /etc/rc. Cheers. Yes, I don't see these errors. But some scripts can change execution order without anchors like mountall For example, adding ldconfig dependancy directly into named brings this order: root@girvas-gw:/etc/rc.d# rcorder -k FreeBSD -s nostart * 2/dev/null ldconfig initdiskless initrandom dumpon vinum Isn't this wrong? Sergey -- Sergey S. Mokryshev [EMAIL PROTECTED] SMP453, MOKR-RIPN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
