http://bugzilla.suse.com/show_bug.cgi?id=904828
--- Comment #19 from Guido Berhörster
pm-utils hooks expect to be able to inhibit suspend/hibernate through exit codes. Currently there seems to be no way to emulate that behavior with systedmd's hooks.
(In reply to Wolfgang Bauer from comment #17)
(In reply to Guido Berhörster from comment #16)
Configuration variables and user scripts could be supported although I don't know if that would interfere with what systemd does e.g. with clock sync after wakeup.
Well, but on second though just calling all scripts in /usr/lib/pm-utils/sleep.d/ might interfere as well.
E.g. /usr/lib/pm-utils/sleep.d/99Zgrub (part of pm-utils) has been replaced with /usr/bin/systemd-sleep-grub (which is called by systemd-hibernate.service) in 13.2. So the work it's supposed to do will actually be done twice which might lead to problems.
So at least now unnecessary scripts should be removed from pm-utils first, I'd say.
While it's possible and I'd be willing to fix and expand the script to read configuration from /etc/pm/config.d and to treat /etc/pm/sleep.d as pm-utils does, I'm no longer convinced it is a good idea to try to emulate pm-utils for the above reasons. What is needed is 1. a followup to issues raised in the thread starting at http://lists.opensuse.org/opensuse-factory/2013-11/msg00911.html 2. an assessment of functionality present in pm-utils but not in systemd and a port of that to use systemd hooks in order to avoid regressions 3. a port of any remaining packages which are dependent on pm-utils to systemd hooks 4. the removal of pm-utils from Factory and that's the responsibility of the pm-utils and systemd maintainers. Until that can be done, I'd suggest removing the compatibility script again and restoring Forward-suspend-hibernate-calls-to-pm-utils.patch for all openSUSE versions, see sr#262325. I am also going to fix storage-fixup to use systemd hooks because the current silent failure can do actual physical harm to laptop harddisks without people noticing. -- You are receiving this mail because: You are on the CC list for the bug.