On Wed, 29 Apr 2009, Gavin Atkinson wrote: > On Wed, 2009-04-29 at 11:56 +0930, Daniel O'Connor wrote: > > 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.. > > Odd. What does "rcorder /etc/rc.d/*" show? > > The rc.d REQUIRE lines should prevent this from happening: (this is > on a RELENG_7 system, but it should be similar on HEAD) I've attached the output. > ga9_at_buffy% grep REQUIRE /etc/rc.d/syslogd > # REQUIRE: mountcritremote cleanvar newsyslog > > ga9_at_buffy% grep REQUIRE /etc/rc.d/mountcritremote > # REQUIRE: NETWORKING FILESYSTEMS cleanvar ipsec > > ga9_at_buffy% grep REQUIRE /etc/rc.d/NETWORKING > # REQUIRE: netif netoptions routing network_ipv6 isdnd ppp > # REQUIRE: routed mrouted route6d mroute6d resolv > > (I believe it's netif that configures the network interfaces) Mine's the same.. [inchoate 19:53] ~ >grep REQUIRE /etc/rc.d/syslogd # REQUIRE: mountcritremote cleanvar newsyslog [inchoate 19:53] ~ >grep REQUIRE /etc/rc.d/mountcritremote # REQUIRE: NETWORKING FILESYSTEMS cleanvar ipsec [inchoate 19:53] ~ >grep REQUIRE /etc/rc.d/NETWORKING # REQUIRE: netif netoptions routing network_ipv6 ppp # REQUIRE: defaultroute routed mrouted route6d mroute6d resolv I can't find any reference to syslogd outside of the syslogd rc.d script either.. Argh! I've replaced syslogd with a script which logs where it's being run from so hopefully that will be more illuminating. -- 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