"Tanja Striepling" wrote: > Hi Dischi, > > freevo-devel@lists.sourceforge.net schrieb am 18.04.05 10:04:40: >> >> "Tanja Striepling" wrote: >> > Would it be possible to put the setting of the wakeup time somewhere >> > in the recordserver, so that the time is set everytime the schedule >> > changes? >> >> Yes and no. I only want one app to set the wakeup time. Maybe you have >> a second app running needing a wakeup, e.g. a epg grabber each night >> at 2 a.m. > > Right, that would be more complicated... > So maybe we need an extra instance for handling the wakeup events. > Or maybe make the wakeup wishes of other apps a kind of pseudo recording... > This becomes more a question of design here. > I just think, it would be good, if the next wake up is scheduled as soon as > possible > and not only on shutdown.
It is done that way. When the shutdown helper has a new wakeup time,
it is set, even when it is not running shutdown. You may have an delay
of 30 minutes max. 30 minutes is the max delay the helper asks for the
status. So when the status is asked, the scheduke changes, at least 30
minutes later the wakeup time is set.
Is that what you want?
> There could be several possible ways to shutdown the system.
Yes, and it is now. But between schedule a new program and shutdown
you need at least 30 minutes. But I often just call halt. But that is
also not so good, system shutdown should not work when freevo is busy
(not idle, busy).
So maybe write something like 'freevo showdown now'. This will connect
to the running shutdown helper and should shutdown the system without
checking idletime and apps. Only respect wakeuptime and busy
(recording now).
> The shutdown helper is just one possibility, although in my opinion the most
> important.
> But the user can also choose to shutdown the system from the menu.
> As far as a understand the code, in that case no wakeup would be scheduled.
The wakeup is scheduled in the shutdown helper.
> Moreover a shutdown from a ssh shell or from pressing the power
> button are possible. Maybe the user even choose to not shutdown his
> system automatically at all, but always manually, but still want to
> have the wakeup feature.
A bit strange. The computer wakes up and will never shut down. Anyway,
you could add 'python' to the list of important programs. This way,
the helper won't shut down when python is running == never.
> Sorry, I thought all this would not be so complicated when I made that
> suggestion.
> Still I hope you find the time to think of it.
I'm noy sure if I understand the problem. It should work even on power
failure or the user calling 'halt'. I have the system running for
month and it's working perfect [1]
Dischi
Footnotes:
[1] Except that wakeup on lan which I'm using only works when the
computer has power between shutdown and wakeup (e.g. no power
failure)[2]
[2] This is no problem because the wakeup time is stored in RAM of my
Linksys Router, a power failure would destroy this information.
--
"Real stupidity beats artificial intelligence every time."
-- Bursar 1 - Hex 0 (Terry Pratchett, Hogfather)
pgpHXtYRaBWO7.pgp
Description: PGP signature
