View Single Post
Old 10-06-2016, 10:28 AM   #291
Alan_S
Evangelist
Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.
 
Alan_S's Avatar
 
Posts: 446
Karma: 1084584
Join Date: Aug 2007
Location: Sisak, Croatia
Device: Kobo Aura H2O, Kobo Aura ONE
Quote:
Originally Posted by tshering View Post
I personally do not see a need of a greater accuracy of time keeping as we already have. Another point is, that I would like to keep away from changing to many things outside of KSM. And since there are ways to power off without KSM being informed, we would have to handle this on a more central place. That makes it a non-KSM issue.
Actually, I completely agree with you that this isn't KSM issue.

But, I'm referring on your question if we should handle synchronizing hardware clock at powering off versus immediately.

In my opinion, from KSM's perspective, the best course is to immediately synchronize it with system clock, as soon as we set clock (as it is now done by settime.sh script). And maybe, add some additional code in KSM's poweroff script, just in case, if you want to do this, or think there is need to do this.

What other scripts do is outside KSM's scope. And clock would be as accurate as possible, through KSM or some other software.
Alan_S is offline   Reply With Quote