[vdr] Re: Yet another nvram wakeup problem

[Sergei Haller <Sergei.Haller@math.uni-giessen.de>]

On Mon, 22 Mar 2004, Ora Järvinen (OJ) wrote:

OJ> >
OJ> >> If I do something like
OJ> >>
OJ> >> nvram-wakeup -s $((`date +%s` + 1200))
OJ> >> lilo -R PowerOff
OJ> >> reboot
OJ> >>
OJ> >> the system wakes up as specified. [...]
OJ> >>
OJ> >> Mar 18 12:28:20 vdr shutdownvdr: Next Timer in 21 minutes, shutting
OJ> >> down with: /etc/init.d/vdr stop ; sleep 1 ;
OJ> >> /usr/sbin/specialshutdown
OJ> >
OJ> > you have to check that /usr/sbin/specialshutdown does what you want
OJ> > it to do.
OJ> 
OJ> Currently, it does exactly the same thing that works manually:
OJ> 
OJ> TITLE="PowerOff"
OJ> lilo -R $TITLE
OJ> shutdown -r now

then it should behave the same as in your manual run. but as I have just 
seen in your first mail:

OJ> nvram-wakeup -s $((`date +%s` + 1200))

OJ> Mar 18 12:28:20 vdr vdr-addon-nvram-wakeup: /usr/sbin/nvram-wakeup -ls
OJ> 1079610600 -C /etc/nvram-wakeup.conf

the options for nvram-wakeup are different on the command line and from
the script. May it be that the configuration file specified from the
script (-C /etc/nvram-wakeup.conf) contains incorrect or not all needed
options?

If it works manually without using that file, just stop using it from the 
script.

c ya
        Sergei
-- 
--------------------------------------------------------------------  -?)
         eMail:       Sergei.Haller@math.uni-giessen.de               /\\
-------------------------------------------------------------------- _\_V
Be careful of reading health books, you might die of a misprint.
                -- Mark Twain


-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.