01-16-2014, 01:27 PM
|
#9
|
|
BLAM!
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
The framework & powerd stop is fairly useless in your situation, and actually counter productive if you want a togglable solution to keep the device usable.
I'd go with either tweaking the cronjob programmatically, which isn't necessarily pretty or sane; or a for-ever loop in a background process that you just start/stop as needed.
|
|
|