Carlos E. R. wrote:
On 2017-04-05 14:33, Per Jessen wrote:
Carlos E. R. wrote:
El 2017-04-05 a las 12:44 +0200, Per Jessen escribió:
Carlos E. R. wrote:
Per Jessen [05.04.2017 07:42]: > David C. Rankin wrote: ... Try to set MAIL_CREATE_CONFIG="no" in /etc/sysconfig/mail :)
It might be outdated, since the file speaks about SuSEconfig, but it may still work.
I have it to "no" in this machine, but I don't remember if I did that myself. This system has been upgraded from years ago.
The settings is still present in leap422 and it is set to "yes".
There is also /etc/sysconfig/postfix with a gazillion settings.
If you can, try a new system, set it to "no", then repeat your steps.
I could easily do that, but it's not really important, the results ought to be the same:
with MAIL_CREATE_CONFIG="no" - my changes to main.cf are not touched when I start postfix. with MAIL_CREATE_CONFIG="yes" - my changes to main.cf are not touched when I start postfix.
So, no change either way?
That's what it ought to be, yes. Unless I have used YaST to configure postfix, the postfix config should be left to me. The postfix startup service unit should not touch main.cf when it isn't supposed to, in particular not when I've edited it.
I suppose the script only does that change "sometimes": the first time, and later when sysconfig changes.
The trick is to either use YaST a single time, or to change that variable. I think.
Sure, there are plenty of work-arounds, but that is not the issue. I can also make a backup, then copy that into place once postfix has been started the first time. I thought this was new with Leap422, but I see it in 12.3 and 13.[12] too. In both cases though, I had amended the service unit to work with multiple postfix instances, and disabled the config fixer crud. So I never saw the issue until now. -- Per Jessen, Zürich (14.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org