the issue: i'm in a situation where my service quits after a few seconds of CPU usage (i.e. the default-respawn-limit is not triggered). therefore shepherd keeps restarting it, practically in a busy loop.
suggested solution: maybe respawn-service should check for the disabled state, so that the admin can intervene by `herd disable myservice`. a longer term solution could be to add a respawn-delay field for <service>, and default it to something non-zero. -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- The mind: an excellent servant, but a dangerous master.
