Today it seems this is mostly used by mail and printer servers, and it's not clear to me at all what the property is that makes /var/spool/<package> the better place for the relevant data than /var/lib/<package>. Hence, in the interest of shortening the spec, let's not mention the dir anymore. In particular as the dir really isn't used by us much, for example we do not have a counterpart for RuntimeDirectory=, StateDirectory=, … that would cover the spool. Since most systems these days we care about probably come *without* a printer or mail server, let's maybe no mention this in the man page that is supposed to discuss the rough skeleton how things are set up. After all, people are supposed to exend the skeleton with their stuff, and this sounds more like a case for an extension of the skeleton instead of being considered part of the skeleton itself.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
