FS#13705 - Syslog 3.0.1-4 shuts down if config file from package is written as .pacnew file
Attached to Project:
Arch Linux
Opened by Mårten Olsson (maos) - Sunday, 08 March 2009, 22:47 GMT
Last edited by Aaron Griffin (phrakture) - Monday, 09 March 2009, 19:58 GMT
Opened by Mårten Olsson (maos) - Sunday, 08 March 2009, 22:47 GMT
Last edited by Aaron Griffin (phrakture) - Monday, 09 March 2009, 19:58 GMT
|
Details
Description:
If the config file is written as /etc/syslog-ng.conf.pacnew then syslog-ng will shut down after printing a lot of warnings (which for me scrolled of the top of my screen). This of course stops the log-files from being updated. During some other update the user modified config file was saved as .pacsave and the new config file overwrote the config. When this update goes to core my opinion is that this update should do the same thing with the config file (and printing a warning when upgrading). Additional info: * package version(s) testing/syslog-ng 3.0.1-4 * config and/or log files etc. /etc/syslog-ng.conf /etc/syslog-ng.conf.pacnew Steps to reproduce: have a usermodified config file for syslog-ng and update to latest version in testing. |
This task depends upon
Closed by Aaron Griffin (phrakture)
Monday, 09 March 2009, 19:58 GMT
Reason for closing: Not a bug
Additional comments about closing: This case is covered by a post-install message as is the norm with changes of this type.
Monday, 09 March 2009, 19:58 GMT
Reason for closing: Not a bug
Additional comments about closing: This case is covered by a post-install message as is the norm with changes of this type.
Alternative is of course to have it has a news item or similar to make users really pay attention that this can happen.
I know this is not a bug as such but more "I think this needs to be handled in a way to really keep the syslog running".
And it was maybe wrong to open this bug... But I really think special steps (soemhow) should be taken to keep the syslog running when getting this update.
IF the daemon is restarted, I expect it will error, as the 3.X series has config file changes. But I don't see how this affects a RUNNING daemon. Could you provide some of the error messages?
Must stop writing these things late at night....
[
Attention syslog-ng update:
Configuration file syntax has changed. Make sure to update /etc/syslog-ng.conf
]
That was the point of this - the config file syntax changed and user intervention is needed. Remember: Arch doesn't hold your hand for these things.