mirror/openrc
1
0
Fork 0
mirror of https://github.com/OpenRC/openrc.git synced 2026-01-26 08:27:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

service-script-guide: improve markup

Browse Source 
Now it renders nicer.
This commit is contained in:
fkobi 2025-04-29 12:44:45 +00:00 committed by navi
parent 0026e6a1ee
commit 35b7fd889b
1 changed files with 9 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
service-script-guide.md
View File

@ -20,9 +20,9 @@ Service scripts are shell scripts. OpenRC aims at using only the standardized
POSIX sh subset for portability reasons. The default interpreter (build-time
toggle) is `/bin/sh`, so using for example mksh is not a problem.
OpenRC has been tested with busybox sh, ash, dash, bash, mksh, zsh and possibly
others. Using busybox sh has been difficult as it replaces commands with
builtins that don't offer the expected features.
OpenRC has been tested with busybox's sh, `ash`, `dash`, `bash`, `mksh`, `zsh`
and possibly others. Using busybox's sh has been difficult as it replaces
commands with builtins that don't offer the expected features.
The interpreter for service scripts is `#!/sbin/openrc-run`.
Not using this interpreter will break the use of dependencies and is not
@ -75,22 +75,17 @@ depend() {
}
```
`need` declares a hard dependency - net always needs to be started before this
- `need` declares a hard dependency - net always needs to be started before this
service does
`use` is a soft dependency - if dns, logger or netmount is in this runlevel
- `use` is a soft dependency - if dns, logger or netmount is in this runlevel
start it before, but we don't care if it's not in this runlevel.
`want` is between need and use - try to start coolservice if it is
- `want` is between need and use - try to start coolservice if it is
installed on the system, regardless of whether it is in the
runlevel, but we don't care if it starts.
`before` declares that we need to be started before another service
`after` declares that we need to be started after another service, without
- `before` declares that we need to be started before another service
- `after` declares that we need to be started after another service, without
creating a dependency (so on calling stop the two are independent)
`provide` allows multiple implementations to provide one service type, e.g.:
- `provide` allows multiple implementations to provide one service type, e.g.:
`provide cron` is set in all cron-daemons, so any one of them started
satisfies a cron dependency