mirror of
https://github.com/systemd/systemd
synced 2024-07-21 18:24:38 +00:00
110ba0ccf9
The existing caching policy was completely bogus. In the first stanza, despite the comment, the pattern given would consider the cache invalid if it was more than 1 hour old. The second stanza was also incorrect, since the output of `systemctl --all` is not unit file paths, but unit names. When they were being tested against the cachefile mtime, the test would always fail becuase of the nonexistant file (hopefully). In fact it's not very useful to test if the unit files have newer mtime in this case anyway, since we are only caching their names. Also, `systemctl --all` is an unfortunately slow operation to be used in testing for the cache validity — we want this operation to at least be faster than rebuilding the cache. I've rewritten this stanza with my best guess at its original intent. It now checks against the mtime of the parent directories in the search path, which should be updated and cause the cache to rebuild when we add, remove, or rename any unit files. |
||
|---|---|---|
| .. | ||
| _bootctl | ||
| _busctl | ||
| _coredumpctl | ||
| _hostnamectl | ||
| _journalctl | ||
| _kernel-install | ||
| _localectl | ||
| _loginctl | ||
| _machinectl | ||
| _networkctl | ||
| _oomctl | ||
| _resolvectl | ||
| _sd_hosts_or_user_at_host | ||
| _sd_machines | ||
| _sd_outputmodes | ||
| _sd_unit_files | ||
| _systemctl.in | ||
| _systemd | ||
| _systemd-analyze | ||
| _systemd-delta | ||
| _systemd-inhibit | ||
| _systemd-nspawn | ||
| _systemd-path | ||
| _systemd-run | ||
| _systemd-tmpfiles | ||
| _timedatectl | ||
| _udevadm | ||
| meson.build | ||