Re: is reparent_to_init a good thing to do?

BALBIR SINGH
2001-10-10T13:02:04Z

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

Balbir Singh wrote:

> Rob Landley wrote:
>
>> 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).
>>
>> 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.
>
> 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?

Balbir

>
> comments,
> Balbir
>
>
>

[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 853 bytes --]

----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------