Files
systemd/man
Yu Watanabe fe9bccb2b7 Make new sd-path configuration search functionality generic (#39684)
Reverts systemd/systemd#38680

After taking a closer look I'm not convinced by the approach, see below.

First of all, all other SD_PATH_SEARCH_* are either somewhat generic,
i.e. encode the common prefix for configurations, binaries, etc., or are
subdirectories under systemd/ hence in our own "domain". The
tmpfiles/sysctl/binfmt we don't prefix with "systemd" precisely because
the concept is generic and there're actually other impls of them. A
specific SD_PATH_SEARCH_SYSCTL doesn't fit into our existing scheme.
Instead something along the lines of "SEARCH_SYSTEM_CONFIGURATION" shall
be introduced, and consumers will just suffix
sysctl.d/tmpfiles.d/binfmt.d for the final result.

And secondly, I don't grok why systemd-sysctl now unnecessarily calls
into sd-path to obtain the fixed search path. None of our other tools do
that.

-----------

An alternate approach, SD_PATH_SYSTEM_SEARCH_CONFIGURATION, which does
exactly above, will be introduced instead. It provides a universal
interface for querying any system config with our idiomatic
/etc/:/run/:/usr/local/lib/:/usr/lib/ hierarchy.
2025-11-15 10:09:19 +09:00
..
2024-12-25 17:00:31 +01:00
2024-11-24 01:11:42 +09:00
2025-09-18 10:57:38 +01:00
2025-08-11 10:30:26 +02:00
2025-10-05 05:45:21 +09:00
2025-08-10 13:40:32 +02:00
2025-08-11 10:30:26 +02:00
2025-10-04 18:13:27 +02:00
2025-04-07 16:56:09 +09:00
2025-08-11 10:30:26 +02:00
2025-08-11 10:30:26 +02:00
2024-12-25 17:00:31 +01:00
2024-12-25 17:00:31 +01:00
2024-12-25 17:00:31 +01:00
2025-08-10 13:40:32 +02:00
2024-12-25 17:00:31 +01:00
2025-08-11 10:30:26 +02:00
2025-08-04 05:30:16 +09:00
2025-05-15 02:56:30 +09:00
2025-08-11 10:30:26 +02:00
2025-07-16 05:47:38 +09:00
2025-08-14 23:33:39 +09:00
2024-11-06 19:06:40 +09:00
2025-09-18 10:57:38 +01:00
2024-11-18 15:18:26 +09:00