Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
I refer to bug 909134 - if the administrator stops a service, it may happen that it gets started via socket activation. This is undesired in many cases and breaks backwards compatibility of the service command. Manually stopped service should stay stopped until it gets manually started again (while "manually" means also as a dependency of another manually started service, or by explicit runlevel/target switch, which includes also reboot - masking the service instead of stopping it isn't an option here).

*** Bug 815243 has been marked as a duplicate of this bug. ***

There are multiple reasons why I don't want to do this.
1) it would brake behavior of systemctl
2) service did not support socket activation in previous releases (xinetd), so current behavior is actually an improvement
3) service command never guaranteed that the service will be stopped forever, it could be started again by some other daemon even in the older releases
4) use mask --runtime which is specifically designed for this purpose
5) there is a warning that service could be started again

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.