rtcwake Question

Reed · 17. Dezember 2015

I'm testing rtcwake having it turn off the machine then back on in 60 second using :

Code

rtcwake -m off -s 60

It calls shutdown, but apparently it needs different options than what rtcwake used because it returns with an error about the flags. I've played around with the shutdown command and the correct shutdown command is "shutdown -hP 0" (in 0 seconds shutdown then halt/power-off). If I just type "shutdown" I'll get a similar text from shutdown saying the arguments aren't correct.

Code

root@OpenMediaVault:~# rtcwake -m off -s 60
rtcwake: wakeup from "off" using /dev/rtc0 at Thu Dec 17 07:15:13 2015
shutdown: -H and -P flags can only be used along with -h flag.
Usage:    shutdown [-akrhPHfFnc] [-t sec] time [warning message]
                  -a:      use /etc/shutdown.allow
                  -k:      don't really shutdown, only warn.
                  -r:      reboot after shutdown.
                  -h:      halt after shutdown.
                  -P:      halt action is to turn off power.
                  -H:      halt action is to just halt.
                  -f:      do a 'fast' reboot (skip fsck).
                  -F:      Force fsck on reboot.
                  -n:      do not go through "init" but go down real fast.
                  -c:      cancel a running shutdown.
                  -t secs: delay between warning and kill signal.
                  ** the "time" argument is mandatory! (try "now") **

Alles anzeigen

I installed Debian 7.9.0 then OMV on-top of that install. I can think of a couple of ways around the issue, but I'm perplexed why rtcwake would call shutdown in a way that doesn't work.

Ideas? Thanks in advance!

Reed · 17. Dezember 2015

Looking in the source code for rtcwake it looks to be using:

Code

else if (strcmp(suspend, "off") == 0) {
              char *arg[4];
              int i = 0;


              arg[i++] = _PATH_SHUTDOWN;
              arg[i++] = "-P";
              arg[i++] = "now";
              arg[i]   = NULL;


              execv(arg[0], arg);

Alles anzeigen

It is running "shutdown -P now" and it needs the -h as in "shutdown -hP now" to work. It seems like the -h should be implied with the -P, but here I am. Thoughts?

tinh_x7 · 17. Dezember 2015

Why you don't use rtcwake -m disk -s 60 instead?
I think 60 seconds is too short for the machine to turn off and wake up.
Give it time to stop the necessary task/jobs before it shutdown; maybe 10 minutes.

Reed · 17. Dezember 2015

I could get around this by other means, ie creating a separate cron job with the appropriate shutdown command and then using rtcwake without the need to use 'off'. However, I'm worried that I missed something in setting up Debian 7.9.0 then installing OMV (this was done so I could use UEFI mode on the MB).

Also, 60s is sufficient to shutdown. It takes it ~18 sec to shutdown.

Reed · 18. Dezember 2015

I've been digging into this more and I think my shutdown operates differently, requiring slightly different options than other examples I've found on the internet. Most show the command to poweroff as "shutdown -P now".

Could someone post what info is shown when they type the "shutdown" command? Here's what I see:

Code

root@OpenMediaVault:~# shutdown
Usage:    shutdown [-akrhPHfFnc] [-t sec] time [warning message]
                  -a:      use /etc/shutdown.allow
                  -k:      don't really shutdown, only warn.
                  -r:      reboot after shutdown.
                  -h:      halt after shutdown.
                  -P:      halt action is to turn off power.
                  -H:      halt action is to just halt.
                  -f:      do a 'fast' reboot (skip fsck).
                  -F:      Force fsck on reboot.
                  -n:      do not go through "init" but go down real fast.
                  -c:      cancel a running shutdown.
                  -t secs: delay between warning and kill signal.
                  ** the "time" argument is mandatory! (try "now") **

Alles anzeigen

tinh_x7 · 18. Dezember 2015

I usually use shutdown -h now or poweroff .

Code

SYNOPSIS
       /sbin/shutdown [-akrhPHfFnc] [-t sec] time [warning message]


DESCRIPTION
       shutdown  brings  the system down in a secure way.  All logged-in users
       are notified that the system is going down, and  login(1)  is  blocked.
       It is possible to shut the system down immediately or after a specified
       delay.  All processes are first notified that the system is going  down
       by the signal SIGTERM.  This gives programs like vi(1) the time to save
       the file being edited, mail and news processing programs  a  chance  to
       exit  cleanly,  etc.   shutdown  does  its  job  by signalling the init
       process, asking it to change the runlevel.  Runlevel 0 is used to  halt
       the  system, runlevel 6 is used to reboot the system, and runlevel 1 is
       used to put to system into a state where administrative  tasks  can  be
       performed; this is the default if neither the -h or -r flag is given to
       shutdown.  To see which actions are taken on halt  or  reboot  see  the
       appropriate entries for these runlevels in the file /etc/inittab.


OPTIONS
       -a     Use /etc/shutdown.allow.


       -k     Don't  really shutdown; only send the warning messages to every‐
              body.


       -r     Reboot after shutdown.


       -h     Halt or power off after shutdown.


       -P     Halt action is to turn off the power.


       -H     Modifier to the -h flag.  Halt action is to halt  or  drop  into
              boot  monitor on systems that support it.  Must be used with the
              -h flag.


       -f     Skip fsck on reboot.


       -F     Force fsck on reboot.


       -n     [DEPRECATED] Don't call init(8) to do the  shutdown  but  do  it
              ourself.  The use of this option is discouraged, and its results
              are not always what you'd expect.


       -c     Cancel a waiting shutdown. ("shutdown now" is  no  longer  wait‐
              ing.)  With this option it is of course not possible to give the
              time argument, but you can enter explanatory  message  arguments
              on the command line that will be sent to all users.


       -t sec Tell  init(8)  to wait sec seconds between sending processes the
              warning and the kill signal, before  changing  to  another  run‐
              level.


       time   When to shutdown.


       warning message
              Message to send to all users.

Alles anzeigen

Reed · 18. Dezember 2015

I confirmed these are the same.

Does it give you an error when you type "shutdown -P now"?

Code

root@OpenMediaVault:~# shutdown -P now
shutdown: -H and -P flags can only be used along with -h flag.
Usage:    shutdown [-akrhPHfFnc] [-t sec] time [warning message]
                  -a:      use /etc/shutdown.allow
                  -k:      don't really shutdown, only warn.
                  -r:      reboot after shutdown.
                  -h:      halt after shutdown.
                  -P:      halt action is to turn off power.
                  -H:      halt action is to just halt.
                  -f:      do a 'fast' reboot (skip fsck).
                  -F:      Force fsck on reboot.
                  -n:      do not go through "init" but go down real fast.
                  -c:      cancel a running shutdown.
                  -t secs: delay between warning and kill signal.
                  ** the "time" argument is mandatory! (try "now") **
root@OpenMediaVault:~#

Alles anzeigen

subzero79 · 18. Dezember 2015

Zitat von Reed

shutdown: -H and -P flags can only be used along with -h flag.

Says there use with the -h flag

Reed · 18. Dezember 2015

Yes!

So why is there a mismatch between how our 'shutdown' actually works and how our rtcwake/general Debian works?

subzero79 · 18. Dezember 2015

Sometimes a visit to the debian bug web page

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648449

Reed · 18. Dezember 2015

Thank you. I wasn't aware of the bug tracking location.

It says it is fixed in >2.23 version.

Version installed is 2.20. Current version is 2.27.

I'm new to this, so I'm not sure why apt-get update / apt-get upgrade (or the OMV GUI update) isn't listing the package 'util-linux' as an upgrade.

subzero79 · 18. Dezember 2015

Debian won't upgrade the package, they don't upgrade versions in the middle of the cycle, they are frozen a few month before the release, unless is a security patch. You can try an build your own util-linux package.

rtcwake Question

Jetzt mitmachen!

Tags