From Fedora Project Wiki
| Line 32: | Line 32: | ||
== writing units == | == writing units == | ||
* organization of manpages: systemd.unit, systemd.exec, systemd.service, ... | * organization of manpages: systemd.unit, systemd.exec, systemd.service, ... | ||
* good practices, note some bad ones | |||
== patching daemons == | == patching daemons == | ||
Revision as of 10:07, 11 May 2012
introduction
quickstart, cheat sheet
for users
theory of operation
- initial system setup, manager loop
- units
- their types
- dependencies
- ordering
- requirement
- jobs
- types, transactions, installed jobs
- cgroups
- socket activation
usage, detailed
- everything about systemctl
- overriding units, .include
- systemd-cgls
- systemd-analyze
- separately? journalctl, loginctl, systemd-nspawn
diagnosing problems
- common issues
- increasing verbosity
- log targets
- early shell
- kbrequest
- startup, shutdown
for developers
writing units
- organization of manpages: systemd.unit, systemd.exec, systemd.service, ...
- good practices, note some bad ones
patching daemons
- racy fork+exit
- sd_notify()
- sd_listen_fds()
- password agent