[email protected] schrob: > lrwxrwxrwx 1 root root 27 Jan 14 2021 /etc/sv/xinetd/supervise -> > /run/runit/supervise.xinetd > > The last line above flashes reverse video on a red background; a hint > that /run/runit/supervise.xinetd doesn't exist.
...yet. Correct tho. > So xinetd failed to start. No, not because of that. See below. > I've read https://docs.voidlinux.org/config/services/. No mention of > /run/<anything>. /run/<anything> is an implementation detail not worthy of being mentioned. :) The interesting part is https://docs.voidlinux.org/config/services/#enabling-services ln -s /etc/sv/<service> /var/service/ > How does runit start a service? runsvdir will (within 5s) notice that /var/service/xinetd/ has appeared, and then start "runsv xinetd". > Where in the process is /run/runit/supervise.<service> created? runsv will notice that ./xinetd/supervise is a dangling symlink, and create the directory (assuming /run/runit/ exists). > A fix for this failure? The only failure appears to be that you didn't enable the service before expecting it to work. Otherwise, what's the output of "sudo sv start xinetd"? cheers, Jan
signature.asc
Description: PGP signature
