Hello list,
Yesterday and today, I've been busy either patching boxes for the BIND advisory that we received on the 23rd (when they were running 8.1 or 8.2-RELEASE), or upgrading them (when running 8.0-RELEASE). Today I've come across 2 boxes running 8.2-STABLE and of course, the BIND patch wouldn't apply correctly. I've decided to cvsup them to 8.2-RELEASE and "upgrade" them to it. I've gone through the following steps: - make buildworld - make buildkernel - make installkernel - nextboot -k my new kernel, to ensure it worked fine - rebooted again with the new kernel, this time correctly installed as /boot/kernel - installed the world - run mergemaster -FiPU - rebuild ports Now, I'm facing this odd situation where, just after booting, I get this on the 2 boxes: root 22 0.0 0.0 8256 1876 v0 Is+ 7:32PM 0:00.03 sh /etc/rc autoboot root 1250 0.0 0.0 18000 2576 v0 I+ 7:32PM 0:00.04 /usr/local/sbin/rsyslogd -a /var/run/log -a /var/named/var/run/log -i /var/run/syslog.pid -f /usr/local/etc/rsyslog.conf root 1790 0.0 0.0 8256 1952 v0 I+ 7:32PM 0:00.00 sh /etc/rc autoboot root 1793 0.0 0.0 8256 1952 v0 I+ 7:32PM 0:00.00 sh /etc/rc autoboot Does anybody have an idea why I get these stuck "sh /etc/rc autoboot" processes ? Any pointers as to where I should look ? /var/run/dmesg.boot doesn't give much useful info. They're backup firewalls so I can run complementary tests on them as required. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
