Immanetize (talk | contribs) (→systemd: - restructuring) |
Immanetize (talk | contribs) (→systemd: PrivateTmp changes) |
||
| Line 10: | Line 10: | ||
For more details and examples, see `man 1 systemd-analyze`. | For more details and examples, see `man 1 systemd-analyze`. | ||
== PrivateTmp == | |||
Services with a PrivateTmp= directory defined in their configuration make use of a private temporary directory that is shared by all processes of the service. These temporary files are deleted when the service is stopped. | |||
[[Category:Docs Project]] | [[Category:Docs Project]] | ||
[[Category:Draft documentation]] | [[Category:Draft documentation]] | ||
[[Category:Documentation beats]] | [[Category:Documentation beats]] | ||
Revision as of 02:41, 15 April 2013
This beat is now ready to have Fedora 25 content added by the beat writer
systemd
Modular service configuration with drop-in files
systemd will now look for configuration directives for a service as /etc/sytemd/system/foobar.service.d/*.conf, making site-specific changes easier to deploy and distribute .
graphing the boot process
- systemd-analyze can now use the GraphViz dot tool to generate graphs of the boot process. GraphViz can be installed with yum install graphviz and will create a representation of the full boot process with systemd-analyze dot | dot -Tsvg > systemd.svg More refined plots can be generated with the optional arguments "--order" "--require" "--from-pattern=" and "--to-pattern="
For more details and examples, see man 1 systemd-analyze.
PrivateTmp
Services with a PrivateTmp= directory defined in their configuration make use of a private temporary directory that is shared by all processes of the service. These temporary files are deleted when the service is stopped.