| |||||||||||||
Control Centre: The systemd Linux init system (The H)Control Centre: The systemd Linux init system (The H)Posted May 8, 2012 23:26 UTC (Tue) by skitching (subscriber, #36856)In reply to: Control Centre: The systemd Linux init system (The H) by geuder Parent article: Control Centre: The systemd Linux init system (The H)
Seems like it would be a good idea for systemd to log a warning for any file in /etc/systemd whose timestamp is older than the file of the same name in /lib/systemd.
(Log in to post comments)
Control Centre: The systemd Linux init system (The H) Posted May 9, 2012 16:07 UTC (Wed) by jspaleta (subscriber, #50639) [Link]
Now that... is an interesting idea.
-jef
Control Centre: The systemd Linux init system (The H) Posted May 11, 2012 7:48 UTC (Fri) by jschrod (subscriber, #1646) [Link]
Since many use cases for /etc/systemd unit files just include the respective /lib/systemd file and add a dependency or similar simple extensions, that won't work.
Control Centre: The systemd Linux init system (The H) Posted May 11, 2012 16:14 UTC (Fri) by jimparis (subscriber, #38647) [Link]
> Since many use cases for /etc/systemd unit files just include the respective /lib/systemd file and add a dependency or similar simple extensions, that won't work.
Why not? You'd still get the warning that /lib/systemd/foo was newer than /etc/systemd/foo. And that would let you know to double-check that things are still OK, and to touch /etc/systemd/foo when you're satisfied.
The case where a timestamp check _would_ fail is if the /lib files retain their upstream timestamps rather than the installation timestamps -- then upgrading systemd might install a "new to you" config file that's still older than the last time you touched the corresponding file in /etc.
|
|||||||||||||