gharris999;425990 Wrote:
My preference would be to keep SrvrPowerCtrl's blocking mechanism
simple: a set block blocks all actions, period. Setting a block ought
to be, imho, at the discretion of any plugin's author. Let them decide
if they think their process is important and ought not to
mavit;427770 Wrote:
I feel some bitwise | coming on.
Ahh...I'm hesitant to go down that road. Even though the possible
SrvrPowerCtrl actions are set in stone now, will they always be that way
in the future? I can easily imagine someone extending SrvrPowerCtrl by
making it xml aware and
I think we need to have a think about the possible use-cases for this
feature. This should provide answers to the following questions:
- Should only restart and shutdown events be blocked, and suspend and
hibernate actions be allowed to proceed regardless?
- Should only idle and
Although it goes against your third bullet, I could easily add a setting
to disable the SrvrPowerCtrl interaction if it's causing trouble and
would be of help.
I don't use SrvrPowerCtrl personally so I've never actually seen the
interaction in practice.
Stuart
On Sat, 2009-05-23 at 05:20
Blocks are placed through the CLI or in perl within a plugin. Blocks
have a name and unique ID; you set the name and get returned the ID when
requesting a block. You can clear a block by specifying its ID.
You can list current blocks and loop to clear each one.
You can even, from the CLI, wipe a
mavit;425905 Wrote:
Are there any other plugins currently in existence that block
SrvrPowerCtrl? A quick web search didn't find any.
I implemented the blocking mechanism at the suggestion of PeterW for
his KitchenTimer plugin. I don't know if he ended up using it, though.
Why wouldn't you
mavit;425905 Wrote:
I think we need to have a think about the possible use-cases for this
feature. This should provide answers to the following questions:
- Should only restart and shutdown events be blocked, and suspend
and hibernate actions be allowed to proceed regardless?
LazySearch blocks SrvrPowerCtrl from hibernating while it is performing
lazyfication. I've run into a few bugs with the implementation of this,
but the question that springs to mind is this: why is this desirable in
the first place? Surely if hibernation is allowed to go ahead, the
lazyfication
One thing I know: you can ask srvPowerControl not to take actions. You
can't ask it what it is going to do next, and that may be reboot, or
shutdown completely.
--
epoch1970
epoch1970's Profile:
mavit;425705 Wrote:
LazySearch blocks SrvrPowerCtrl from hibernating while it is performing
lazyfication. I've run into a few bugs with the implementation of this,
but the question that springs to mind is this: why is this desirable in
the first place? Surely if hibernation is allowed to
10 matches
Mail list logo
