Hi, I have an odd problem with my 3 week old -current install - syslogd isn't started. Or rather, it is started before lo0 is up and it fails to start, eg.. Apr 29 11:13:05 inchoate kernel: /dev/ad0s3a: FILE SYSTEM CLEAN; SKIPPING CHECKS Apr 29 11:13:05 inchoate kernel: /dev/ad0s3a: clean, 381721 free (3297 frags, 47303 blocks, 0.7% fragmentation) Apr 29 11:13:05 inchoate kernel: /dev/ufs/inchoatevar: FILE SYSTEM CLEAN; SKIPPING CHECKS Apr 29 11:13:05 inchoate kernel: /dev/ufs/inchoatevar: clean, 417071 free (4815 frags, 51532 blocks, 1.0% fragmentation) Apr 29 11:13:05 inchoate kernel: /dev/ufs/inchoateusr: DEFER FOR BACKGROUND CHECKING Apr 29 11:13:05 inchoate kernel: Apr 29 20:42:48 syslogd: bind: Can't assign requested address Apr 29 11:13:05 inchoate kernel: Apr 29 20:42:48 syslogd: bind: Can't assign requested address Apr 29 11:13:05 inchoate kernel: syslogd: Apr 29 11:13:05 inchoate kernel: child pid 285 exited with return code 1 Apr 29 11:13:05 inchoate kernel: Apr 29 11:13:05 inchoate kernel: /etc/rc: WARNING: failed to start syslogd Apr 29 11:13:05 inchoate kernel: Additional ABI support: Apr 29 11:13:05 inchoate kernel: linux Apr 29 11:13:05 inchoate kernel: . Apr 29 11:13:05 inchoate kernel: Starting wpa_supplicant. Apr 29 11:13:05 inchoate kernel: Starting Network: lo0 bfe0. Apr 29 11:13:05 inchoate kernel: add net ::ffff:0.0.0.0: gateway ::1 I put '/etc/rc.d/syslogd restart' in rc.local but that's only a work around. I ran mergemaster -s and it did find a few changes (worringly) but the rc.d ones were just removing 'noprofile' from the keyword line which I don't think would affect things. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:46 UTC