On 2022-10-18 00:58, Laurent Bercot wrote:
> > By testing I meant checking if the directory has an active process
> > watching it. I believe there is a function in skalibs fd_lock [1]
> > that svscan uses to check if another svscan runs there. I think it is
> > just a matter of exposing that function as standalone executable.
>
> There are no executables to test whether s6-svscan or s6-rc are
> running on a given directory, because these are not dynamic properties.
> By policy, decided by you or your distro, you should *know*, at all
> times, whether a given directory is a scandir with an s6-svscan running
> on it - or whether a given directory is a livedir with s6-rc running
> on it.
> If you think a given directory should have an s6-svscan running on it,
> then you're right; ensure that s6-svscan is started at boot time, and
> write your scripts assuming that it's there. If something fails because
> it's not there, that's a bug or a system problem, and needs to be fixed,
> not accommodated by your scripts.
>
These tests made sense in the situation of user's services as systemd
does it. (Like answering a question whether another login shell has
already spawned svscan) It is indeed not necessary with static user
tree.
Ihor
Received on Tue Oct 18 2022 - 05:12:13 CEST