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:
Enabling service using 'systemctl enable <servicename>' yields confirmation message "Created symlink from <location1> to <location2>". This confirmation message is not printed on stdout, but on stderr. This is a problem since it creates unwanted output on stderr if 'systemctl enable <servicename>' is part of service installation script.
How reproducible:
It is always reproducible
Steps to Reproduce:
(service being enabled must be previously disabled to see the confirmation message 'systemctl disable <service name>')
1. run 'systemctl enable <service name> 1>/dev/null'
2. prints "Created symlink from <location1> to <location2>" => it's printed on stderr
(service being enabled must be previously disabled to see the confirmation message 'systemctl disable <service name>')
1. run 'systemctl enable <service name> 2>/dev/null'
2. prints nothing => message was on stderr
Expected results:
I expect the confirmation to be printed on stdout
(In reply to Lukáš Nykrýn from comment #2)
> --quiet ?
Well that's not the point. I'm not asking how to hide the output. I'm trying to point out that this particular message should be printed on standard output and it pollutes error output.
Anyway I would not be able to pass any arguments to the systemctl command, I'm in no conrol of the script which calls it. All I do is process the stdout and stderr.
I would say that this is correct behavior, the output is more a status message and it should not be process by a pipe with some additional program.
If you really think that this behavior should change, please file an upstream issue github.com/systemd/systemd/issues.