gharris999;594340 Wrote: > Presumably, the system won't sleep while the timer is waiting since the > 'NoSleep' assertion isn't released until after the timer has fired. Not quite. You can force the system to sleep manually. (Apple menu item, 'Sleep'). This will override any 'NoSleep' assertions in force. An alternative approach might be to catch the system has woken event, and end at that point. Agree doesn't seem to be a biggie. gharris999;594340 Wrote: > A bigger problem, as I see it, involves updating the plugin. I'm not > sure exactly what happens when SBS tries to update the plugin while the > "old" sleep-inhibit is executing. I'm going to have to figure out an > approach for this one. > Have the tool write out its PID to a known file and have SBS kill it from that ? Alternatively have SBS execute the tool through a script, and let the script handle the killing of an existing instance. Not unlike a system daemon start-up script. I haven't examined how SBS launches the tool.
Example: SleepWatcher will write out its PID if asked - I have used that for a similar purpose in the past. gharris999;594340 Wrote: > > SrvrPowerCtrl's EOD function needs will probably fill your needs. Thanks. > I'll explore this further in the New Year. I think I did pick up on the sudoers configuration. -- mrw ------------------------------------------------------------------------ mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=48521 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
