Christoph Anton Mitterer
843262fa5f
All currently ignored extensions either “belong” to some other program (and may thus be used, changed or interpreted by that) or imply a certain meaning (like `bak`, `old` and `new`). This adds the more generic extension `ignore` which is meant to imply no purpose whatsoever. A use case would be the following scenario: One might want to share a drop-in configuration over multiple units like in: `/etc/systemd/system/a.service/foo.conf` and `/etc/systemd/system/b.service/foo.conf`, which then would be symbolic links to the actual file. Of course one could place that actual file in a directory that is not parsed by systemd, but it is unit-configuration after all, so it would be nice to have it somewhere beneath `/etc/systemd/system` (or other parsed directories). However, placing it there needs a way to ensure that it’s never accidentally used by systemd, which this extension is meant for.
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
Repositories with distribution packages built from git main are available on OBS