Re: start order on 5.2.1
Hi J.D. The runorder of the rc scripts in /etc/rc.d is determined by the dependencies of these scripts, There is a utility called rcorder(8) (read the manpage!) which returns the names in the order they can be executed. It uses special comments in order to do so. So you probably just have to add: # REQUIRE: ldconfig to your dns startscript to fix your startup. Kind regards, Alex. J.D. Bronson wrote: I noticed that my new 9.3 version of bind needs a shared library which is not available until ELF ldconfig runs. Why is named starting before than and how can I change that so that ldconfig runs as early as possible? Jul 9 19:48:35 bacardi kernel: Mounting NFS file systems: Jul 9 19:48:35 bacardi kernel: . Jul 9 19:48:35 bacardi kernel: Starting syslogd. Jul 9 19:48:35 bacardi kernel: Jul 9 19:48:35 bacardi syslogd: kernel boot file is /boot/kernel/kernel Jul 9 19:48:35 bacardi kernel: Starting named. Jul 9 19:48:35 bacardi kernel: /usr/libexec/ld-elf.so.1: Jul 9 19:48:35 bacardi kernel: Shared object libgcc_s.so.1 not found Jul 9 19:48:35 bacardi kernel: Jul 9 19:48:35 bacardi kernel: Starting ntpdate. Jul 9 19:48:41 bacardi kernel: ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/BerkeleyDB.4.2/lib ..after boot, if I startup named manually it works fine. thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: start order on 5.2.1
At 08:17 AM 07/13/2004, Nagilum wrote: Hi J.D. The runorder of the rc scripts in /etc/rc.d is determined by the dependencies of these scripts, There is a utility called rcorder(8) (read the manpage!) which returns the names in the order they can be executed. It uses special comments in order to do so. So you probably just have to add: # REQUIRE: ldconfig to your dns startscript to fix your startup. Kind regards, Alex. Alexyes - this is what I came up with over the weekend and it works fine. I filed a bug on this, since nothing should really be starting prior to ldconfig running (at least in my mind). I dont understand though why it 'suddenly' became an issue, but at least my work-around (and your idea too) did the trick. thanks. -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
start order on 5.2.1
I noticed that my new 9.3 version of bind needs a shared library which is not available until ELF ldconfig runs. Why is named starting before than and how can I change that so that ldconfig runs as early as possible? Jul 9 19:48:35 bacardi kernel: Mounting NFS file systems: Jul 9 19:48:35 bacardi kernel: . Jul 9 19:48:35 bacardi kernel: Starting syslogd. Jul 9 19:48:35 bacardi kernel: Jul 9 19:48:35 bacardi syslogd: kernel boot file is /boot/kernel/kernel Jul 9 19:48:35 bacardi kernel: Starting named. Jul 9 19:48:35 bacardi kernel: /usr/libexec/ld-elf.so.1: Jul 9 19:48:35 bacardi kernel: Shared object libgcc_s.so.1 not found Jul 9 19:48:35 bacardi kernel: Jul 9 19:48:35 bacardi kernel: Starting ntpdate. Jul 9 19:48:41 bacardi kernel: ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/BerkeleyDB.4.2/lib ..after boot, if I startup named manually it works fine. thanks! -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
