On 2019-04-08 18:38:46 +0200, Stefan Sperling wrote: > On Mon, Apr 08, 2019 at 05:05:47PM +0200, Vincent Lefevre wrote: > > Well, I forgot, there's at least an issue with svnserve. I got that > > in the past, and could reproduce it: once I kill the svn client > > with Ctrl-C and kill the SSH master too, the sshd terminates, but > > svnserve is still running, and now has 1 as its PPID: > > > > UID PID PPID C STIME TTY TIME CMD > > vlefevre 48724 1 0 12:40 ? 00:00:00 svnserve -t > > Hmm... that looks like the svnserve process was in zombie state > and is not being terminated. It is the init system's job to call > waitpid() for such processes.
No, it is not in zombie state. It is still running. > > If svnserve was waiting for something from sshd, it should at least > > have noticed that the connection is no longer there. > > There is no connection as far as svnserve is concered. > In tunnel mode, svnserve reads from stdin and write to stdout, and > it is done when these get closed or the process is terminated for > some reason. Yes, but that's how it is connected to sshd. The parent process (sshd) has died. So, if svnserve was reading from the pipe, it would have got an error. > I suspect the problem is caused either in SSH or somewhere else on > your server. It cannot be SSH, since SSH has terminated but svnserve was still running. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
