Systemd: Difference between revisions

From DWIKI
mNo edit summary
Line 61: Line 61:


  journalctl --vacuum-size=1G
  journalctl --vacuum-size=1G
===Journal settings===
/etc/systemd/journald.conf
SystemMaxUse=1G
and then
systemctl restart systemd-journald.service


== Analyze boot processes ==
== Analyze boot processes ==

Revision as of 11:58, 9 March 2022

 


Documentation

Locations

/etc/systemd
/usr/lib/systemd/
/lib/systemd

 


HOWTO

Timers

man systemd.timer

List active timers

systemctl list-timers


List all timers

systemctl list-timers --all

Create timer

systemctl enable fstrim.timer


FAQ

Fix journal size

journalctl --vacuum-time=10d

or

journalctl --vacuum-size=1G

Journal settings

/etc/systemd/journald.conf

SystemMaxUse=1G

and then

systemctl restart systemd-journald.service


Analyze boot processes

systemd-analyze blame

 

 

 

Systemd and DNS

resolvectl status

Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.

Means systemd-resolved is not running

Restart:

systemctl restart systemd-resolved
      
      

 

Add nameserver

Sacrifice a chicken

 

Flush caches

systemd-resolve --flush-caches

All status

systemctl status -a

syslog spam

https://psyq123.wordpress.com/2015/06/29/if-you-get-a-lot-of-logspam-from-systemd-in-your-varlogsyslog-this-might-help/

list available services

systemctl list-unit-files

or

systemctl list-units

 

normal interface names

net.ifnames=0

Show failed services

systemctl --failed

 

systemd: Started Session

Change loglevel to notice in /etc/systemd/system.conf

systemctl daemon-reexec

Status

Active: inactive (dead)

parameter ActiveState would return inactive

SubState returns dead