On Monday 18 April 2005 17:19, Dirk Meyer wrote:
> It is done that way. When the shutdown helper has a new wakeup time,
> it is set, even when it is not running shutdown. [...]
Great to hear this, this is more like the solution I had in mind. Maybe I
overlooked the announcement on freevo-devel?! ;-)
> So when the status is asked, the scheduke changes, at least 30
> minutes later the wakeup time is set.
>
> Is that what you want?
This sounds like a cool way; of course some signalling (MBUS?) instead of
polling would be even better, no?
> 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).
Oh, and I wondered why I did not get too much feedback on my shutdown ideas.
(At least, lately Tanja seems to have tied up with my and Georg's stuff.)
Nice to see that so many of my plans are already put into code! :-)
This is all 2.0, right? What are the definitions of "busy"? (You mentioned a
"list of important programs"?) Oh, now that I have a little more time than
lately, I feel that'll become Freevo time again! ;-)
> [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.
Geeky setup! ;-) (Programmed WOL by Router..)
Ciao, / /
/--/
/ / ANS
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel
