Re: [Devil-linux-develop] syslog-ng and inability to login

[Heiko Z. <he...@zu...>]

Quoting Bruce Smith <bw...@re...>:

>>>>>>> Syslog-ng works fine with the default config, but not if you upgrade
>>>>>>> an older system.
>>>>>>> Can we add something simple to upgrade-config to make the upgrade
>>>>>>> life easier?
>>>>>>
>>>>>> Hmm... Probably we can try to apply the diff for syslog-ng config,
>>>>>> I think on
>>>>>> most systems the diff should apply, because the changes affect only
>>>>>> main options.
>>>>>
>>>>> It shouldn't be a problem unless they customized their syslog-ng config.
>>>>> And if they customized it, there is a really good chance a patch
>>>>> would fail.
>>>>>
>>>>> I'm not sure of the best solution for this.
>>>>
>>>> There's not too much we can do if folks change their config files, but
>>>> I think we should be able to modify those specific lines if they're
>>>> not changed.
>>>
>>> If the config file hasn't changed, it should update to the new version
>>> by default.  Isn't that the way it works?
>>
>> That is correct.
>> But isn't it highly likely that somebody added lines for i.e. a remote
>> log? At least I have all my servers set up this way.
>
> It seems like the last time I looked, those lines are already in the
> config file commented out, so all you have to do is uncomment them.
>
> And I don't think a patch will work on a line that has changed at all.
>  Even just a "#" removed.

Another options would be using sed and just replacing the lines in question.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.