If I add a service to the /etc/inetd.conf (for example I un-comment the
FTP entry there) and send “kill -SIGHUP [inetd’s PID]” - the super-server
survives and adds a service indeed.
If I try removing a service by commenting it’s entry out and send the same
“kill -SIGHUP [inetd’s PID]” - the super-server allways dies…
This does not depend on the actual service added|removed, inetd allways
adds successfully and allways fails to survive the removal.
If I add a service to the /etc/inetd.conf (for example I un-comment the
FTP entry there) and send “kill -SIGHUP [inetd’s PID]” - the super-server
survives and adds a service indeed.
If I try removing a service by commenting it’s entry out and send the same
“kill -SIGHUP [inetd’s PID]” - the super-server allways dies…
Yup, does it for me, too.
Looks like a bug in inetd to me.
I’ve issued a PR against this, but do not have any idea when or if a
fix might be made.
I think that:
slay inetd; inetd
would work as a reasonable work around.
(Or,if you prefer:
kill [inetd’s pid]; inetd
But, I like slay, as it saves me having to figure out inetd’s pid from
the ps or sin listing.)
