I notice s6-svscanboot is the start script for s6-svscan. I am not an execline expert, but I can see that s6-svscanboot prepare log directories and start s6-svscan. If systemd provides log service for s6-svscan. Do we need s6-svscanboot for rpm package?
The next question is about s6.pre-install, s6.pre-upgrade script. they do the same thing (setup catchlog user/group), why we need s6.pre-upgrade script if the previous installation already setup the catchlog user/group? Wang > On Apr 8, 2024, at 18:52, Laurent Bercot <ska-skaw...@skarnet.org> wrote: > >> Does s6-svscanboot support reload with kill -HUP? Systemd can specify >> command to to reload the configuration of the service. > > I assume you mean s6-svscan? > > s6-svscan supervises a collection of services, it has no internal state > itself, so "reload" does not really make sense. But if you send a SIGHUP > to it, it will make sure the supervised services are exactly the ones > listed in its scan directory. See > https://skarnet.org/software/s6/s6-svscan.html > > Please ask your questions on the list rather than to me directly. > > -- > Laurent >
