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:
Once we requested feature to see what happens during some stages.
There could be a way of hooking a script into various stages of shutdown/rearly booot
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
there is use case:
Try to execute some command before any other services start (previous rc.sysinit).
Try to execute some command after any other services start (previous rc.local).
Actual results:
Expected results:
user would like to see progress during boot/shutdown
Additional info:
$ man bootup
you can create unit files with "After=" and "Before=" to sort yourself into the bootup sequence.
For /etc/rc.local there is /lib/systemd/system/rc-local.service, which executes /etc/rc.local, if it exists. It is ordered "After=network.target".
As explained already in comment #2 you can create unit files with "After=" and "Before=" to sort yourself into the bootup sequence.
We also still support rc.local, but only for compatibility reasons, the rc.local support is deliberately not advertised in the systemd documentation, since we discourage its use.
The systemd documentation in general does not document deprecated compatibility mechanisms to avoid promoting the use of them, ie it also does not document that the service and chkconfig commands can still be used.