I think there is no weekly programming for EOD, but perhaps you could
use a "blocker" that would inhibit the action until it is removed. You
can set/remove blockers by the command-line or assigning such lines to
a custom command, which would give you menu items to simply click on
the web interface and on the players.
The most recent version of the plugin can also look at the computer's
CPU load, network activity to define if it is the right time to
shutdown. So if you had a remote computer wake the server through the
network, wait a bit and start a network backup transfer, the plugin
might recognize that and refrain from sleeping the machine until the
network transfer is over and files compressed, even if SBS is
completely idle. You'd have to set the appropriate thresholds in the
plugin by trail and error to have this work properly.
Your other question depends on your hardware. Your computer is likely
to support programmed wake-up by the time of day ("ACPI wake"). It is
very likely to support wake-up from network ("wake-on-lan", aka WOL) if
your machine is wired to the router.
What you have to discover by yourself is from which modes these actions
can have an effect. Usually wake-up by ACPI or WOL will work even from
soft-off. However I've had machines which would not WOL from soft-off
and only from suspend. Or a funny one that would hang at shutdown when
a wake-up date was programmed
You should try the various energy saving states on the computer, and
see if the machine wakes up from lan correctly when you activate a
player (for example. Or use your router's web interface to send wol
packets, or the command-line on another computer).
Same goes with the ACPI wake feature: set a date in the future in the
internal clock, and see if the machine revives itself from suspend,
hibernate, soft-off. I won't give you the specific 'date' command-line
to set the alarm time in the computer 10 minutes in the future but this
page might help (see section "Manually test wakealarm")
http://www.mythtv.org/wiki/ACPI_Wakeup
What I have seen on the various machines I have put under power
management is the following:
- some recent machines will draw as little as 1W from soft-off, but
then WOL is not possible. ACPI alarm should be possible (?)
Lack of WOL is generally bad because you can't wake the server from the
SB players.
- wake from suspend will take around 10 seconds from sleep to music
playing on your SB. That's good. Wake from hibernate will take up to
minutes. Wake from soft off will take about the same time as wake from
hibernate. Waiting 2 minutes in front of the SB player is a very, very
long time.
- in suspend, hibernate and regular soft-off mode (not the special 1W
off mode), the computer will draw the same power. Yes, when "off" I've
had machines drawing 13W. 0 W only then the cord was pulled (and then
you drain the internal lithium battery used to maintain BIOS
settings.)
So suspend is the best mode for serving SB players.
- when waking from hibernate and soft-off mode, you may come across
the regular hard drive maintenance time. According to the size and
filesystem on the drive(s), checking may delay effective start for tens
of minutes.
That will never happen if you choose to suspend rather than hibernate
or go soft-off.
In short, I don't see the gain in using any other mode than suspend.
Also:
- make sure your lithium battery is not depleted, or the time of day
in the BIOS might go back to 2001 or something if the computer loses
power, making a programmed ACPI wake ineffective.
- choose to store the system time as UTC in the OS and in the BIOS.
System date stored local time is a Windows complication. If the
computer does not boot windows, use UTC in the BIOS (at OS level Linux
does that by default normally, so you just have to worry about a
possible BIOS setting.)
Using UTC allows to handle better DST changes. Mixing UTC and local
time will create a mess with the OS defining a date for ACPI wake and
the BIOS rejecting it as being in the past (e.g. by one hour), or
waking later than you'd expect.
- Use the NTP protocol to synchronize the system clock with reference
clocks on the internet, some machines/OSes can make the hardware clock
drift quite a lot, with programmed wake happening at the wrong time.
The NTP daemon looks for other computers dates on the network/internet
and keeps the hardware clock in checks regularly. Beware that firewalls
may block NTP, which uses port 123/udp. Perhaps your router/firewall
wants to act as a reference clock for your LAN, if so that is probably
what you want to use.
NTP will give you time accuracy of the second on every machines in your
network, sparing you with weird issues when you browse to secure web
sites (eg "Warning: This site's certificate is not yet/no longer
valid") and allowing to compare log files on 2 machines easily (eg for
backups, looking at the client log and looking at the server's log)
--
epoch1970
Daily dose delivered by: 3 SB Classic, 1 SB Boom iPeng (iPhone + iPad)
SqueezeCenter 7.4.2 (Debian 5.0) with plugins: MusicIP Server Power
Control by Gordon Harris WeatherTime by Martin Rehfeld IRBlaster by
Gwendesign (Felix) Find cover art by bpa BBC iPlayer, SwitchPlayer
by Triode PowerSave by Jason Holtzapple TrackStat, Song Info, Song
Lyrics by Erland Isaksson SaverSwitcher, ContextMenu by Peter
Watkins.
------------------------------------------------------------------------
epoch1970's Profile: http://forums.slimdevices.com/member.php?userid=16711
View this thread: http://forums.slimdevices.com/showthread.php?t=48521
_______________________________________________
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins
