Red Hat Bugzilla – Bug 840014
systemctl disabled sendmail comes back again after upgrade.
Last modified: 2015-02-18 08:44:50 EST
Description of problem:
This seems to be a generic systemd problem: systemd-adapted services assume themselves to always run when installed, whereas I just like to have service ready & around for reference, and do not want to run them all the time. (see my other filing on rpcbind also).
In a nutshell, I found that doing
systemctl disable sendmail.service
systemctl stop sendmail.service
removes the service files from /etc/....../multi.users.wants/ , but they are readded after a unsual yum upgrade. This is wrong and not like how it was with sysv (i.e.disable service is persistent across upgrade).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.systemctl disable sendmail.service
systemctl stop sendmail.service
2. yum upgrade
sendmail runs again.
disabled services remain disabled.
Same problem with F18 rawhide.
But I don't know if it's a problem with update of sendmail or update of systemd.
I am afraid it is currently not possible. The service settings is updated during upgrades according to your alternatives settings (alternatives --config mta). You need to have one system MTA, that is always active e.g. to forward important system messages to admin. There is NO MTA effort:
But AFAIK it is still not completed.
The spec could be patched not to start the MTA if there is no MTA enabled. All MTAs would have to be patched (i.e. sendmail, postfix, exim).
The proposal makes sense. Moving to rawhide, because this change needs to be synchronized accross all MTAs.
Just for info F18 rawhide
Today there is an update for systemd.
After reboot sendmail-service is not re-enable also I think that the problem is with sendmail package...
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.