doc:appunti:linux:sa:systemd_tmpfiles_problem
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
doc:appunti:linux:sa:systemd_tmpfiles_problem [2024/02/26 09:43] – [Analyzing Systemd] niccolo | doc:appunti:linux:sa:systemd_tmpfiles_problem [2024/02/26 09:50] (current) – [Analyzing Systemd] niccolo | ||
---|---|---|---|
Line 31: | Line 31: | ||
systemd-analyze verify default.target | systemd-analyze verify default.target | ||
</ | </ | ||
+ | |||
+ | The command highlights an **ordering cycle** problem, which causes the deleting of a service: | ||
+ | |||
+ | < | ||
+ | sockets.target: | ||
+ | sockets.target: | ||
+ | ... | ||
+ | sockets.target: | ||
+ | cycle starting with sockets.target/ | ||
+ | ... | ||
+ | </ | ||
+ | |||
+ | Notice that the ordering (and the deleting choice) is not deterministic: | ||
The problem was introduced by this custom Postfix/ | The problem was introduced by this custom Postfix/ | ||
**[[postfix_courier_authdaemon_debian_12]]**. In fact disabling the Systemd '' | **[[postfix_courier_authdaemon_debian_12]]**. In fact disabling the Systemd '' | ||
- | In my specific case the problem was solved changing the dependencies of the **[[https:// | + | In this specific case the problem was completely |
doc/appunti/linux/sa/systemd_tmpfiles_problem.1708937025.txt.gz · Last modified: 2024/02/26 09:43 by niccolo