This bug is trivial to reproduce--just start the echo service and leave it open and then run "/etc/init.d/xinetd restart" and you'll easily reproduce.
By adding --retry 2 to the stop argument, you are sending signal 3 to the xinetd process and giving that 2s to succeed after which time the s-s-d retry sends a KILL signal. This is what actually makes the stop work. I believe this is the right thing to do. However, a rather large side effect is that you will in fact terminate xinetd's service processes. A reproduction can also be done (though it takes much longer) without any connections to running services as the initial signal 3 can take time to handle and the start stop daemon sees that the process is still running (that it tried to kill) so it doesn't start a new one. This reproduction done on Lenny. I'd recommend for xinetd that the user either add "--retry 2" to this rc script or that the package maintainer add it to the package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
