The /usr/share/hibernate/scriptlets.d/clock script installed by sys-power/hibernate-2.0-r4 runs the wrong script to save/restore the clock. For gentoo, ClockSave runs: /etc/init.d/clock.sh stop > /dev/null 2>&1 ClockRestore runs: /etc/init.d/clock.sh start > /dev/null 2>&1 Since /etc/init.d/clock.sh doesn't seem to exist, surely both it should be running /etc/init.d/hwclock in both cases? (In practice, only the restore is done by default because /etc/hibernate/common.conf has the line 'SaveClock restore-only'.) Reproducible: Always
Also, as "/etc/init.d/hwclock start" wouldn't work if the service is already in the started state, it would have to have to be called with specific actions to save or restore the clock. The /etc/init.d/hwclock script already has a "save" action. Perhaps it should have a "restore" action as well. Then the /usr/share/hibernate/scriptlets.d/clock script could run /etc/init.d/hwclock save > /dev/null 2>&1 to save the clock, and /etc/init.d/hwclock restore > /dev/null 2>&1 to restore the clock.
This package is now orphan: http://my.opera.com/pacho/blog/2012/11/27/about-maintainer-needed
+ 17 Dec 2012; Sergey Popov <pinkbyte@gentoo.org> + +files/hibernate-script-baselayout2-clock.patch, + -hibernate-script-2.0-r4.ebuild, +hibernate-script-2.0-r5.ebuild: + Revision bump: EAPI 5, fix incorrect clock script name wrt bug #406065, drop + old revision Please test