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
| Linus Torvalds | Linux 2.6.27-rc8 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Linux 2.6.20-rc6 |
| Mike Snitzer | Re: Distributed storage. |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Herbert Xu | Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state ch... |
