Hello,
I was setting up a central logserver this afternoon and some of the

functionality I need wasn't in the stock syslogd(8), so I chose to use

syslog-ng.
I noticed that you cannot specify syslogd=NO or syslogd_flags=NO to

disable it (in rc.conf.local), and I was mostly curious why.
I'm sure it has something to do with the gap between when things start

up and may need to log vs. when the local startup happens -- if that's

true, what is the suggested way around that?
Originally I thought to simply keep syslogd enabled, but syslog-ng

will not be able to start in that case.
Is my best option to kill syslogd from rc.local or manually edit /etc/rc?
Thanks for any suggestions.
Kian

How about leaving them both running, and binding syslog-ng to just

the relevant IP address?

Thank you all for the suggestions.  For some reason I didn't think of

what Stuart suggested, so I'll try that out.  I think it is better

than modifying rc(8).
I think I will have the stock syslogd do it's thing default thing and

maybe even forward messages to syslog-ng in addition so there is some

consistency with the rest of the hosts.
Thanks again,

Kian

modify /etc/rc (this looks questionable anyway -- looks like someone

snook the named stuff in there because it needs  aprivate log device in

the chroot):
echo 'starting system logger'

rm -f /dev/log
if [ X"${named_flags}" != X"NO" ]; then

        rm -f /var/named/dev/log

        syslogd_flags="${syslogd_flags} -a /var/named/dev/log"

fi

if [ -d /var/empty ]; then

        rm -f /var/empty/dev/log

        mkdir -p -m 0555 /var/empty/dev

        syslogd_flags="${syslogd_flags} -a /var/empty/dev/log"

fi

syslogd ${syslogd_flags}
----------

echo 'starting system logger'

if [ X"${syslogd_flags}" != X"NO" ]; then

    rm -f /var/named/dev/log

    rm -f /dev/log

    mkdir -p -m 0555 /var/empty/dev

    syslogd_flags="${syslogd_flags} -a /var/empty/dev/log"

    syslogd ${syslogd_flags}

fi
then syslogd_flags=NO in rc.conf(5).
~BAS
--

Brian A. Seklecki <bseklecki@collaborativefusion.com>

Collaborative Fusion, Inc.
IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited.  Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.