On Tue, Jan 28, 2025 at 5:02 PM Patrice Duroux <patrice.dur...@gmail.com> wrote:
>
> Of course, maybe I misspoke but my point wasn't about the configuration files
> remaining as expected just removing the package and not purging it. It is
> about
> the broken symlink to its service file which is for sure no more present
> whatever a removal or a purge. Or is such a symlink considered as part of
> configuration files? I don't think so, but I might be wrong.
Related (it does not answer your question), you can find the broken
symlinks related to systemd with:
symlinks -r /etc/systemd | grep dangling
The command does not tell you how or why they became broken.
And you can remove them with:
symlinks -r -d /etc/systemd
Some old programs use non-existent symlinks to store or persist state
information rather than create a normal file. But I don't believe
systemd uses the technique.
Jeff
