> You'd still have a PID reuse race. Of course, you could also
> cover this by checking the process' start time ...
Good point. It is unlikely this will happen in our scenario (very long-lived
processes), but we should certainly cover that case.
> But just designing the parent to be simple enough to be reliable
> and/or generic enough that it doesn't even need to be upgraded
> still looks like a more promising approach to me.
That would be the simple solution. However, it doesn't cover the case of a
cosmic ray causing a segfault, or the OOM killer coming along, or root
accidentally doing a kill -9 on the wrong pid, or other similar issues.
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/