Woof commented this morning on another way of recovering from a supervisor crash... something about forking a child but dong anything unless/until the parent dies and then not exec'ing but running as a copy of itself (i.e. a new supervisor)... I don't think this removes the need to restart the supervisor and all its original children, but I might not have understood entirely. Can you provide more details?
Does anyone have any experience with "seteuid, setegid - set effective user or group ID" or "setreuid, setregid - set real and/or effective user or group ID", which sound like they might allow supervisor to drop to user-level permissions for most things, but retain the right to return to root? Otherwise I think I have to use a wrapper program to invoke sipxpbx restart as root. Carolyn
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
