<[email protected]> wrote:
> May I ask you devs to put a note on it into
> http://man.openbsd.org/apmd.8
> as there is currently no description of `apmd`
> waiting for `/etc/apm/*` executables to finish
> without processing new calls in the meantime.
I don't see what to add, because it is obvious.
> May I ask you to also add a warning that self-lock will occur
> if the user intends to call `apm` from `/etc/apm/*`
You made up the word self-lock.
> And may I ask you to also add hints on workarounds
> like backgrounding (`apm &`) or running
> yet another script, in background again, from `/etc/apm/*` scripts.
That won't work.
> From my user perspective, such self-lock peculiarity looks like
> a mechanism flaw
> and I hope it will be resolved in future versions.
> I myself can't help with code enhancement, sorry.
It is not a flaw.
apm communicates with the Advanced Power Management daemon, apmd(8),
making requests
Almost all software of any kind does operations like this syncronously.
> `apmd` apparently doesn't do completely nothing while
> waiting for the script to finish because auto-adjusting of
> `sysctl hw.cpuspeed` & `sysctl hw.setperf`
> does happen dynamically depending upon load.
Wrong: apmd does absolutely nothing to adjust the cpu adjustment.
The kernel does that. The apm and apmd flags for performance adjustment
just instruct the kernel what model to follow. And while that happens,
apmd truly does nothing except wait for apm requests, which it services
syncronously.
