Originally Posted by brunold
|
Kevin,
what should I say, you know that story about the left and the right hand when one does not know what the other is doing ?
When I check the sysconfig file for syslog, there is the following section in:
|
Code:
|
# cat /etc/sysconfig/syslog
...
# If you don't want to let SuSEconfig generate your
# syslog-ng configuration file, set this to "no".
#
# SuSEconfig is using a template configuration file
# /etc/syslog-ng/syslog-ng.in
# you can adopt it to your needs instead...
#
SYSLOG_NG_CREATE_CONFIG="yes" |
So as this is the default config, modifying the syslog-ng.conf is nice, but when the SuSEconfig ran the next time it will modify it using the template. I think there is at least a warning but not sure if yast in the graphical version will show you that.
Therefor I would say use the syslog-ng.in file to add the dhcp settings and run SuSEconfig or change the above settings to disable SuSEconfig doing that.
I will forward this notice to my Novell contact.
I think he loves to check those things.
Rainer
|
Yes, my sysconfig file has that line in it as well about creating the code, but for some odd reason doesn't seem to work properly.
I checked my other server that has DHCP and there's a lot file, just that it's empty and the sysconfig stuff is missing (those 3 lines Novell mentions)
Looks like I need to adjust my instructions some more for some more post-cleanup.