system/systemd
system/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd synced 2024-07-21 10:17:21 +00:00
Code Issues Actions 7 Packages Projects Releases Wiki Activity

docs/TIPS_AND_TRICKS: format text

Browse source
This commit is contained in:
hulkoba 2024-02-26 14:36:37 +01:00
parent 4601153cbe
commit 56a0f583f7
No known key found for this signature in database
GPG key ID: ACB6C4A3A4F2BE2F
1 changed files with 10 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
docs/TIPS_AND_TRICKS.md
View file

@ -155,13 +155,16 @@ $ psc
$ ln -sf /usr/lib/systemd/system/multi-user.target /etc/systemd/system/default.target
```
This line makes the multi user target (i.e. full system, but no graphical UI) the default target to boot into. This is kinda equivalent to setting runlevel 3 as the default runlevel on Fedora/sysvinit systems.
This line makes the multi user target (i.e. full system, but no graphical UI) the default target to boot into.
This is kinda equivalent to setting runlevel 3 as the default runlevel on Fedora/sysvinit systems.
```sh
$ ln -sf /usr/lib/systemd/system/graphical.target /etc/systemd/system/default.target
```
This line makes the graphical target (i.e. full system, including graphical UI) the default target to boot into. Kinda equivalent to runlevel 5 on fedora/sysvinit systems. This is how things are shipped by default.
This line makes the graphical target (i.e. full system, including graphical UI) the default target to boot into.
Kinda equivalent to runlevel 5 on fedora/sysvinit systems.
This is how things are shipped by default.
## What other units does a unit depend on?
@ -172,7 +175,8 @@ $ systemctl show -p "Wants" multi-user.target
Wants=rc-local.service avahi-daemon.service rpcbind.service NetworkManager.service acpid.service dbus.service atd.service crond.service auditd.service ntpd.service udisks.service bluetooth.service cups.service wpa_supplicant.service getty.target modem-manager.service portreserve.service abrtd.service yum-updatesd.service upowerd.service test-first.service pcscd.service rsyslog.service haldaemon.service remote-fs.target plymouth-quit.service systemd-update-utmp-runlevel.service sendmail.service lvm2-monitor.service cpuspeed.service udev-post.service mdmonitor.service iscsid.service livesys.service livesys-late.service irqbalance.service iscsi.service netfs.service
```
Instead of "Wants" you might also try "WantedBy", "Requires", "RequiredBy", "Conflicts", "ConflictedBy", "Before", "After" for the respective types of dependencies and their inverse.
Instead of "Wants" you might also try "WantedBy", "Requires", "RequiredBy", "Conflicts", "ConflictedBy", "Before", "After"
for the respective types of dependencies and their inverse.
## What would get started if I booted into a specific target?
@ -182,4 +186,6 @@ If you want systemd to calculate the "initial" transaction it would execute on b
$ systemd --test --system --unit=foobar.target
```
for a boot target foobar.target. Note that this is mostly a debugging tool that actually does a lot more than just calculate the initial transaction, so don't build scripts based on this.
for a boot target foobar.target.
Note that this is mostly a debugging tool that actually does a lot more than just calculate the initial transaction,
so don't build scripts based on this.