Skip to contentSkip to conversation

is reparent_to_init a good thing to do?

DISCUSSION Jesse Pollard 1 participant 1 message Oct 10, 2001

lore
Share & tools
lore
#0 lore raw

"BALBIR SINGH" <[email protected]>:

Quoted 23 lines
Quoted 21 lines · Balbir Singh
Quoted 8 lines · Rob Landley

Or long lived kernel threads from short lived login sessions.

You have a headless gateway box for your local subnet, administered via ssh from a machine on the local subnet. So you SSH into the box through eth1, ifconfig eth0 down back up again. If eth0 is an rtl8039too, this fires off a kernel thread (which, before reparent_to_init, was parented to your ssh login session).

Quoted 6 lines

Now exit the login session. SSH does not exit until all the child processes exit, so it just hangs there until you kill it from another console window...

Rob

The question one can ask is what should a thread do then? Should reparent_to_init() send a SIGCHLD to the process/task that was parent before init became the parent? this should be easy to do, but will this fix the problem? I think so.

Quoted 7 lines
Quoted 1 line

I can patch up something soon, if somebody is willing to test it.

Ooh! sorry this is a wrong approach to send SIGCHLD to the previous parent. AFAIK, all shells send their children SIGHUP when the shell exits, but SSH may have some special security consideration in waiting for all children to exit, does anyone know?

Not exactly - sshd will not terminate a connection until all forwarded socket connections are terminated. If processes are running in the background, then they will remain after sshd terminates. Foreground processes will terminate as specified by the shell.

If the sshd TCP socket remains open after the network interface is shutdown, then you are into the TCP timeout.. Not a ssh logout.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: [email protected]

Any opinions expressed are solely my own.