Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 26 Mar 2008 15:37:40 +0300
From: "Dmitry V. Levin" <>
Subject: Re: named SysV order seems to be wrong


On Wed, Mar 26, 2008 at 08:08:18AM +0300, (GalaxyMaster) wrote:
> I'd like to point out that it doesn't look right:
> peach!root:~# ls -ld /etc/rc.d/rc3.d/S*{syslog,named}
> lrwxrwxrwx 1 root root 15 Feb 25  2006 /etc/rc.d/rc3.d/S20named -> ../init.d/named
> lrwxrwxrwx 1 root root 16 Oct 25  2005 /etc/rc.d/rc3.d/S30syslog -> ../init.d/syslog
> peach!root:~#
> I think that the syslog service should be started prior any other
> service which wants to use syslog.  Is this a bug or am I missing
> something?

Unless syslog.conf uses remote host names, yes, the "syslog" service
could be started prior to the "bind" service.


Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.