Check out my first novel, midnight's simulacra!
Systemd: Difference between revisions
From dankwiki
(Created page with "I try not to be judgmental, but if someone's complaining about "the good ol' SysVinit days", they're pretty much an idiot. systemd has its flaws, but it's infinitely better th...") |
No edit summary |
||
| Line 1: | Line 1: | ||
I try not to be judgmental, but if someone's complaining about "the good ol' SysVinit days", they're pretty much an idiot. systemd has its flaws, but it's infinitely better than what came before, not an insult ala Upstart, and actually got things moving, so I'm a big fan. | I try not to be judgmental, but if someone's complaining about "the good ol' SysVinit days", they're pretty much an idiot. systemd has its flaws, but it's infinitely better than what came before, not an insult ala Upstart, and actually got things moving, so I'm a big fan. | ||
==User | ==System instance== | ||
===Paths=== | |||
In descending priority: | |||
* /etc/systemd/system: results of <tt>systemctl enable</tt> and system unit extensions | |||
* /run/systemd/system: runtime, systemd-originated units | |||
* /usr/lib/systemd/system: package-originated system units | |||
==User instances== | |||
When enabled, <tt>pam_systemd</tt> launches a single <tt>systemd --user</tt> instance for a user's first login, which is killed when that user's last login exits. User units can neither depend on nor reference system units. | When enabled, <tt>pam_systemd</tt> launches a single <tt>systemd --user</tt> instance for a user's first login, which is killed when that user's last login exits. User units can neither depend on nor reference system units. | ||
===Paths=== | ===Paths=== | ||
In descending priority: | |||
* ~/.config/systemd/user: user-originated units for that's user sessions | * ~/.config/systemd/user: user-originated units for that's user sessions | ||
* /etc/systemd/user: system-wide admin-originated units for user sessions | * /etc/systemd/user: system-wide admin-originated units for user sessions | ||
* ~/.local/share/systemd/user/: package-originated, user-installed units for that user's sessions | * ~/.local/share/systemd/user/: package-originated, user-installed units for that user's sessions | ||
* /usr/lib/systemd/user: package-originated, admin-installed units for user sessions | * /usr/lib/systemd/user: package-originated, admin-installed units for user sessions | ||
Revision as of 14:37, 18 June 2019
I try not to be judgmental, but if someone's complaining about "the good ol' SysVinit days", they're pretty much an idiot. systemd has its flaws, but it's infinitely better than what came before, not an insult ala Upstart, and actually got things moving, so I'm a big fan.
System instance
Paths
In descending priority:
- /etc/systemd/system: results of systemctl enable and system unit extensions
- /run/systemd/system: runtime, systemd-originated units
- /usr/lib/systemd/system: package-originated system units
User instances
When enabled, pam_systemd launches a single systemd --user instance for a user's first login, which is killed when that user's last login exits. User units can neither depend on nor reference system units.
Paths
In descending priority:
- ~/.config/systemd/user: user-originated units for that's user sessions
- /etc/systemd/user: system-wide admin-originated units for user sessions
- ~/.local/share/systemd/user/: package-originated, user-installed units for that user's sessions
- /usr/lib/systemd/user: package-originated, admin-installed units for user sessions
