Systemd Suspend Sedation Problem

Hi, I follow the following wiki page to setup a suspend sedation systemd service. https://wiki.debian.org/SystemdSuspendSedation Code: # /etc/systemd/system/suspend-sedation.service [Unit] Description=Hibernate after suspend Documentation=https:

Re: Suspend-sedation Problem

Quoting Eirik Schwenke (ei...@schwenke.info): > Then there was a different change, to do numerical comparison against date > +%%s. I think the new code contains two errors: a) it should be: > > NOW="$(date +%s)"; > > At least my date complains that % isn't a valid number if "+%%s" is used. > P

Re: Suspend-sedation Problem

Hi, I see there's been some recent changes to the https://wiki.debian.org/SystemdSuspendSedation article. First a change to move from a (my) dumb string check against "/usr/sbin/rtcwake --mode show" output to avoid issues with l10n (while there doesn't appear to be translations for Norwegian,

Re: Suspend-sedation Problem

John Hasler wrote: > I'm trying to get suspend-sedation working on my Gateway 450SX4 with > Jessie installed. Suspend and Hibernate work. I'm following the > instructions at > > https://wiki.debian.org/SystemdSuspendSedation > > When I close the lid the machine suspends properly and wakes up a

Re: Suspend-sedation Problem

Re: Suspend-sedation Problem

Gave up and kludged together a workaround. rtcwake will not return "alarm: off" when run from a systemd service though it will when run from a login shell. The "File exists" message is evidently a red herring. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- To UNSUBSCRIBE, email to deb

Re: Suspend-sedation Problem

I wasn't reloading the script properly. Still doesn't work, but now I see that the "if" is dropping through because rtcwake always returns "alarm: on" even though it must have expired because the script is running. I still get the incomprehensible "file exists" message. -- John Hasler jhas...@n

Re: Suspend-sedation Problem

Additional information: "systemctl suspend" produces exactly the same result as closing the lid except of course that the machine does not go back into suspension after the script runs. "systemctl hibernate" produces exactly the same result as "systemctl suspend" except that the machines goes into