meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
linux:systemd [2017/01/19 21:09] – [tricks] niziak | linux:systemd [2024/02/09 19:24] (current) – niziak | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== systemd ====== | ||
+ | |||
+ | * [[https:// | ||
+ | |||
===== HowTo ===== | ===== HowTo ===== | ||
==== start / stop ==== | ==== start / stop ==== | ||
+ | Rerun all generators, reload all unit files and recreate dependency tree: | ||
<code bash> | <code bash> | ||
systemctl daemon-reload | systemctl daemon-reload | ||
Line 23: | Line 28: | ||
</ | </ | ||
+ | <code bash> | ||
+ | systemd-cgtop | ||
+ | </ | ||
==== emergency mode ==== | ==== emergency mode ==== | ||
Line 148: | Line 156: | ||
You can create refer to device, e.g. create .wants directory | You can create refer to device, e.g. create .wants directory | ||
< | < | ||
+ | |||
+ | === udev: start service === | ||
+ | To start service if device is inserted: | ||
+ | <file | mu.rule> | ||
+ | ..., TAG+=" | ||
+ | </ | ||
=== do not mount crypted volumes === | === do not mount crypted volumes === | ||
Line 166: | Line 180: | ||
TimeoutStartSec=15 | TimeoutStartSec=15 | ||
</ | </ | ||
+ | |||
+ | ====== Issues ====== | ||
+ | |||
+ | ===== init.d services not started ===== | ||
+ | |||
+ | < | ||
+ | systemd-sysv-generator[320]: | ||
+ | systemd-sysv-generator[320]: | ||
+ | systemd-sysv-generator[320]: | ||
+ | </ | ||
+ | |||
+ | Reason is that some init scripts are symlinked to files located in **/opt** directory, which is a different FS (in this case BTRFS subvolume), and it was not mounted when **systemd-sysv-generator** was started. | ||
+ | |||
+ | **Solution: | ||
+ | [[https:// | ||
+ | |||
+ | > Under systemd-enabled systems, there' | ||
+ | > You also need to make sure that your filesystem' | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||