angler-fishThe Vulnerability History Project

service: handle forking services that move to a new PID

      When some forking daemons receive a SIGHUP, they re-execute themselves
and consequently change to a new main PID. As long as they update the
PID file in the right order (before exiting the old PID), we can detect
that and avoid killing them.
    
commit db01f8b3f870611a013b913636bb7fefaab34018
+3 -15
expand_less