Quote:
Originally Posted by GeoffR
I've added this patch to post #2.
The 1-255 minute limit is because a 2-byte "movs" instruction is used to load the values in the code. Loading values larger than 255 requires a 4-byte instruction or multiple instructions, and there is not enough space to fit a larger instruction without re-writing the code, which is a lot of work.
|
thank you very much.
Unfortunately it's not so useful given the limitation on value size (at least to my purpose), but as you explained it's not something that can be fixed patching the libnickel.
Maybe (just for fun) I will try simulating auto-shut down with some cron job, I guess it should be possible.