http://bugzilla.suse.com/show_bug.cgi?id=901115
Bug ID: 901115 Summary: yast2-network overwrites postfix configuration Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: lmb@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: ---
Created attachment 609975 --> http://bugzilla.suse.com/attachment.cgi?id=609975&action=edit main.cf mods caused by yast2 network
After a long time, I used yast2-network to change something in the network configuration of my node. (Changed the hostname.)
As a result, my postfix main.cf was overwritten and rendered unusuable. I'm entirely unsure why some of these parameters were touched - why would it unset mailbox_command, set mailbox_transport, unset relay_host?
Yes, this was facilitated by me having /etc/sysconfig/mail:MAIL_CREATE_CONFIG="yes" at the default value, but normally, none of the yast2 tools overwrites manually modified files silently, without even creating an in-place backup.
Especially since this looks as if unrelated parameters were touched. I might have understood rewriting "mydestination", but the other parameters make absolutely no sense.
I'm attaching the diff here - I restored the main.cf from backup.
http://bugzilla.suse.com/show_bug.cgi?id=901115
Gabriele Mohr gs@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lmb@suse.com Assignee|yast2-maintainers@suse.de |mfilka@suse.com Flags| |needinfo?(lmb@suse.com)
--- Comment #1 from Gabriele Mohr gs@suse.com --- Please attach YaST log-files, see http://en.opensuse.org/openSUSE:Report_a_YaST_bug.
http://bugzilla.suse.com/show_bug.cgi?id=901115
Michal Filka mfilka@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|mfilka@suse.com |varkoly@suse.com
http://bugzilla.suse.com/show_bug.cgi?id=901115 http://bugzilla.suse.com/show_bug.cgi?id=901115#c16
--- Comment #16 from Lars Marowsky-Bree lmb@suse.com --- I agree, I never understood the rationale here. This seemed like a pretty severe bug to me, but I simply gave up.
My suggestion would be, like with other scripts, to detect manual modifications and *not overwrite them*, but place the new files as xxx.new. Or, yes, at the very least *create a backup* of the files you're about to overwrite.
http://bugzilla.suse.com/show_bug.cgi?id=901115
Peter Varkoly varkoly@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |WONTFIX
http://bugzilla.suse.com/show_bug.cgi?id=901115 http://bugzilla.suse.com/show_bug.cgi?id=901115#c19
Peter Varkoly varkoly@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED
--- Comment #19 from Peter Varkoly varkoly@suse.com --- The actual yast2-network does not modify postfix at all.