http://bugzilla.opensuse.org/show_bug.cgi?id=901115
http://bugzilla.opensuse.org/show_bug.cgi?id=901115#c13
Christian Boltz changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |suse-beta@cboltz.de
Resolution|WONTFIX |---
--- Comment #13 from Christian Boltz ---
I just answered a mail on the opensuse-de where an annoyed user wants to know
who destroyed his postfix configuration without any backup :-(
He also posted an interesting log line:
2015-06-23 08:05:25 <1> x220.xx.yy(4275) [Ruby]
network/runtime.rb:41 Updating sendmail and/or postfix configuration.
Since this hit quite some people already (I remember other bugreports about
this), please decide on a solution instead of closing as "wontfix" again.
Possible solutions - please choose one ;-)
- deliver the package with /etc/sysconfig/mail:MAIL_CREATE_CONFIG="no"
(easy to do and avoids surprises, optionally add a note about the changed
default to the release notes)
- make sure config.postfix creates a backup of the config files it overwrites
(use unique backup filenames - filling up /etc/postfix with lots of backups
is harmless compared to overwriting the backup on the second config.postfix
run)
- let config.postfix write to *.new files and ask the user to activate them
_Additionally_ it might be a good idea to do some changes in YaST so that it
doesn't call config.postfix in surprising places. On my system, I found:
# grep -r update.mta.config /usr/share/YaST2/
/usr/share/YaST2/include/network/runtime.rb: def update_mta_config
(that's the function that calls config.postfix)
/usr/share/YaST2/modules/DNS.rb: update_mta_config
/usr/share/YaST2/modules/Lan.rb: update_mta_config if !@write_only
(maybe those modules should use some specific "postconf setting new_value"
calls?)
See also bug 852604, bug 850463, bug 788299 #c5, bug 865132, bug 852604
--
You are receiving this mail because:
You are on the CC list for the bug.