desktop suspends? but reboots on resume as a result of runlevel 0 on resume?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
desktop suspends? but reboots on resume as a result of runlevel 0 on resume?
I have an rsnapshot server that I want to put to sleep and woken up only at nights when I do backups or when I need to restore, which can be done by issuing a wol packet to wake the server up. when I issue pm-suspend the screen goes black and according to pm-suspend.log everything looks to have gone to sleep successfully. that said, I'm not sure it entirely is since the HDD lights are still on... regardless if I issue a wol packet to the server I do see the server resuming, but as soon as it's done it enters into a complete system restart! any ideas?
a snippet from /var/log/messages that leads me to believe suspend and resume are working? but something after is switching the runlevel causing the reboot...
Code:
Mar 25 20:32:21 defiant kernel: [ 1287.324225] PM: resume of devices complete after 25476.675 msecs
Mar 25 20:32:21 defiant kernel: [ 1287.381596] Restarting tasks ... done.
Mar 25 20:32:21 defiant init: Switching to runlevel: 0
the only post I came across describing anything similar is https://www.linuxquestions.org/quest...of-3-a-440716/, but that trailed off with no answer. this system is a Slackware64 system that started with 13.37 and was successfully upgraded to 14.0, then to 14.1 and now 14.2. I had tried suspend/resume under 13.37, but never got it working and haven't tried in between the versions leading up to 14.2. kernel is the generic 4.4.208 with initrd.gz built. any suggestions?
I had something like this. The problem for me was too many things watching the power. I issued a resume in acpid, but XFCE4's power manager was also getting in on the act. So first it did a suspend from one, resumed, and then suspended from the other.
Solution was to disable the XFCE4 Power manager, as disabling acpid wasn't an option.
I had something like this. The problem for me was too many things watching the power. I issued a resume in acpid, but XFCE4's power manager was also getting in on the act. So first it did a suspend from one, resumed, and then suspended from the other.
Solution was to disable the XFCE4 Power manager, as disabling acpid wasn't an option.
hrmm, interesting however as this is somewhat of a headless server I have not used anything X related apps so everything has been purely from the console...
I have a box at home that I use as a jump box. It starts automatically at 9:00PM and runs before automatically shutting down at 12:10AM. (Back in the day when we were allowed out of the house, I could log in remotely and pick up a connection to a work server.)
This is done using 'rtcwake' run as a cron job. From the root crontab on the jump box:
Code:
10 0 * * * /usr/sbin/rtcwake -m off --date 21:00:00
I have a box at home that I use as a jump box. It starts automatically at 9:00PM and runs before automatically shutting down at 12:10AM. (Back in the day when we were allowed out of the house, I could log in remotely and pick up a connection to a work server.)
This is done using 'rtcwake' run as a cron job. From the root crontab on the jump box:
Code:
10 0 * * * /usr/sbin/rtcwake -m off --date 21:00:00
Your hardware would need to support this.
decided to go this route, which definitely does work for my purposes of automatically turning on a few minutes before starting the backup tasks. only issue now is I can't get the system to go into sleep or hibernate, only freeze. that will be another exercise for another time. anyway, thank you for this!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
