Quote:
Originally Posted by hemi_426
lets say sshd or dhcpd how would they refer to syslog-ng cause there is nothing in dhcpd.conf that points to any logging ?
thanks for u reply
|
For those programs (and most others) there is nothing to specify in their configurations (files under /etc). sshd, for instance, allows you to specify the log level, but it does not specify what the log file is. That is handled by your log daemon's configuration. For some other programs, however, their configuration might specify where to log it's information. Typically, these logs are only for that program, however, instead of say one log file that catches many things (like /var/log/syslog).
In short, probably all you have to do is
1) make sure rc.syslog-ng is started during system boot
2) change syslog-ng's config to catch what you want and in what files.
The first one requires a little bit of hacking for slackware, however.
If you don't have a rc.syslog-ng file, then copy whatever startup script syslog-ng has to /etc/rc.d and make it executable. Now, you need to
make sure that all the startup scripts that refer to syslog will now refer to syslog-ng instead. I suggest grepping all the files under /etc/rc.d for syslog. That is
Code:
grep syslog /etc/rc.d/*
Important files that I'm sure will come up will include at least:
rc.M - starts syslog, so change it to syslog-ng
rc.inet1 - set $LOGGER to syslog-ng logger executable
rc.inet2 - tries to start syslog if it isn't already (if /usr is on a network partition). Change this to syslog-ng
If you are lazy you might be able to simply move rc.syslog to a safe place and then symlink rc.syslog-ng to rc.syslog. Even still, you will end up having to modify some startup scripts because they check for /var/run/syslogd.pid, which isn't the process id you care about.
