On 04/14/2017 03:52 PM, Carlos E. R. wrote:
I thought of that, but it needs to be able to inhibit for months. Ie, ignore completely the request to reboot or whatever.
If you enable the inhibiting process as a service on boot, it should block until you tell it to stop manually, either by stopping the service or just killing the process. I haven't investigated it further, but it looks like it could be as simple as starting a process that sets such a lock (I don't know, just set a read that blocks waiting for some input forever, and tag it as an inhibiting process) then it should take no cpu sleeping until you kill it, but effectively prevents reboot or shutdown until you do. I'll have to play with it in my spare time :) -- David C. Rankin, J.D.,P.E.