Messages in this thread |  | | Date | Fri, 09 May 2003 14:54:29 -0400 | From | Chris Friesen <> | Subject | anyone ever implemented a reparent(pid) syscall? |
| |
I've got some other developers wanting some way for a process to be notified on the death of another process. Now I understand that if all the processes are forked by a main one, then the main one will get a SIGCHILD on the death of the other processes.
The problem with this is that if the main one dies, then all the other ones get reparented to init. I would like some way for the main one to restart, read the list of pids out of a file that it conveniently stashed away, and reparent the pids back to itself (the same way that they were reparented to init in the first place) so that it gets SIGCHILD when they die.
Once I have this ability, then it becomes simple for arbitrary processes to register with it so that others can be notified in some standard way if they die.
Has anyone ever done this? Is there any reason why it is a particularly bad idea?
Thanks,
Chris
-- Chris Friesen | MailStop: 043/33/F10 Nortel Networks | work: (613) 765-0557 3500 Carling Avenue | fax: (613) 765-2986 Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |