bin/60237: inetd(8) has no way to reconfigure stream wait processes

["campbell+netbsd%mumble.net@localhost via gnats" <gnats-admin%NetBSD.org@localhost>]

>Number:         60237
>Category:       bin
>Synopsis:       inetd(8) has no way to reconfigure stream wait processes
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 07 23:45:01 +0000 2026
>Originator:     Taylor R Campbell
>Release:        current, 11, 10, 9, ...
>Organization:
The inetgizer Bunny
>Environment:
>Description:

	If you configure a stream-type wait-mode service in
	/etc/inetd.conf, inetd(8) will eagerly bind a listening socket
	and then lazily spawn a subprocess with the listening socket
	passed as fd 0 when the first client tries to connect to it.

	However, while inetd(8) can reload its configuration file on
	SIGHUP and update all other types of services, I can't find any
	path by which it will kill and restart stream-type wait-mode
	services.

	Of course, I can dig through ps(1) output to find the service's
	pid to kill outside inetd(8), but that's not reliable (could
	exit and have its pid recycled, for instance) and inetd(8)
	won't wait for the child to exit before starting a new
	instance (which is important for process limits).

>How-To-Repeat:

	code contemplation

>Fix:

	Yes, please!  Perhaps inetd(8) should send SIGTERM (and maybe
	SIGKILL after a delay) to the child.  Perhaps inetd(8) should
	put the child in its own process group and send SIGTERM to the
	process group.  Perhaps we should ship a more elaborated
	process supervisor with socket activations.  Perhaps we should
	have a pony.