From Gentoo Wiki
< /etc(Redirected from Local.d)
Jump to:navigation Jump to:search

/etc/local.d/ can contain small programs or light scripts to be run when the local service is started or stopped. The local service is part of OpenRC.

Scripts in /etc/local.d/ with the suffix .start will be executed at boot time, scripts with suffix .stop at shutdown time. Scripts should have the execute permission. Files are processed in lexical order.

The local service is intended to execute just a few very light commands and terminate. Read and understand this rest of this section before use.

This system is intended only for very light scripts that will terminate quickly, and are at no risk of hanging, e.g. to write a value to a file in /proc/.

The local service is not considered started or stopped until everything is processed, so if there is a .start or .stop process which takes some time to run, it can delay - possibly even freeze - boot or shutdown.

This infrastructure should not be used to start other scripts or programs in the background. If the /etc/init.d/local service script is restarted several times, then those scripts or programs will be started in the background several times, possibly resulting in race conditions. A .stop script for terminating background processes started this way would be needed, but may easily fail, e.g. if the .start script had been executed several times.

To start a process in the background, write an OpenRC initscript file, as described in the OpenRC Initscripts section of the Gentoo Handbook.


Here is a script simply as an example of what can be put in /etc/local.d/. This script will set parameters for the cpu governor, it is a good candidate to be used with the local service as it simply writes to some files in proc and terminates:

FILE /etc/local.d/cpu_governor.start

#set cpu governors to "performance"
for c in $(ls -d /sys/devices/system/cpu/cpu[0-9]*); do echo performance >$c/cpufreq/scaling_governor; done

Another example: sync local time with google.com on poweroff:

FILE /etc/local.d/date.stop
echo Sync time
date; date -s "$(wget -qSO- --max-redirect=0 google.com 2>&1 | grep Date: | cut -d' ' -f5-8)Z"
sleep 5

Another example: remove sources older than 6 month, on Fridays:

FILE /etc/local.d/eclean.stop
if [ `who -r | awk '{print $2}'` = "0" ] && [ "$(date +%a)" = "Fri" ]; then
    echo Lets remove sources older than 6 month
    eclean-dist --time-limit=6m
    sleep 5
    echo ======= removed old sources =======

Yet another example: trim SSD on poweroff, on Fridays:

FILE /etc/local.d/trim.stop
# From
# https://fitzcarraldoblog.wordpress.com/2018/01/13/running-a-shell-script-at-shutdown-only-not-at-reboot-a-comparison-between-openrc-and-systemd/
if [ `who -r | awk '{print $2}'` = "0" ] && [ "$(date +%a)" = "Fri" ]; then
    echo /etc/local.d/trim.stop: run SSD trim
    fstrim / --verbose
    sleep 5
Remember to mark the script as executable:
root #chmod +x /etc/local.d/<scriptname>.<start|stop>



The local service will usually be started on boot by adding it to the default runlevel (see the next section), however it can be started explicitly:

root #rc-service local start

If the local service is in the default runlevel, but stopped, it can be started by having OpenRC check for stopped services:

root #openrc

Add local service to default runlevel

To start the local.d scripts at boot time, add it to the default runlevel:

root #rc-update add local default


By default, the local service will silence all output. Adding -v option to rc-service will cause it to show which scripts were run and their output, if any:

root #rc-service local restart -v

See also