What do you mean by "run" syslog.conf? /etc/syslog.conf is the configuration for the system logger daemon (syslogd), however SLES10 uses the "new generation" system logger syslog-ng. The configuration file for that is in /etc/syslog-ng/syslog-ng.conf. It looks like SuSE recommend that you edit /etc/syslog-ng/syslog-ng.conf.in and then run SuSEconfig to generate the /etc/syslog-ng/syslog-ng.conf file from it - I haven't done this myself so can't go into much detail.
You should find that this daemon is running already. Once you have updated the configuration file you can make the daemon re-read the file by sending it a HUP signal (kill -HUP <pid>) or by running /etc/init.d/syslog reload.
Yes I mean run syslog.conf and not use syslog-ng at all. It's been hard to find anything on running the old version of syslog on SuSe 10. This is to keep legecy systems and new ones the same for support teams.
Why keep an outdated logger on a new system? I find syslog-ng far superior to syslog in many respects. I think it's time to embrace the forward momentum.
You can always run SLES 8 on a 2.2 kernel without security updates.
Seriously, is there a technical reason for wanting to install syslog on a shiny new OS. I'd be willing to help you out. I manage a few systems with either syslog or syslog-ng and they are not that hard to support. For me using syslog-ng on my servers for centralized logging makes my job a lot easier.
I just ran yast on a SLES 10 system and both packages are available to install, so if you want to stick with the old stuff it should be a matter of simply removing syslog-ng and installing syslogd:
Code:
i syslog-ng 1.6.8 1.6.8 new-generation syslog-daemon 569.8 K
syslogd 1.4.1 The Syslog daemon 51.4 K
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.