Bug 978849

Summary: RFE: hooking a script into various stages of shutdown/rearly booot
Product: Red Hat Enterprise Linux 7 Reporter: Petr Sklenar <psklenar>
Component: systemdAssignee: systemd-maint
Status: CLOSED NOTABUG QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: high    
Version: 7.0CC: harald, hdegoede, systemd-maint-list
Target Milestone: rcKeywords: FutureFeature, Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-06 13:41:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 959971    

Description Petr Sklenar 2013-06-27 08:25:47 UTC 
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:
Comment 2 Harald Hoyer 2013-06-27 10:59:17 UTC 
$ 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".
Comment 3 Harald Hoyer 2013-06-27 11:03:08 UTC 
To see what happens, remove "quiet" from the kernel command line, or inspect the journal after booting.

# journalctl -b
Comment 6 Hans de Goede 2013-08-06 13:41:44 UTC 
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.