Hi Gharris999, It's been a while and I see your plugin is now in RC. From the readme and the thread I see you've done a wonderful job. Over the last few weeks I have been selecting hardware and writing (actually, more testing that coding...) an activity monitor for the general-purpose server I want to setup, inspired by 'this post' (http://forums.slimdevices.com/showpost.php?p=313317&postcount=8) from Syburgh. Right now I have a perl daemon that loops slowly in the background looking for system activity (AFP, SMB, NFS, network traffic, user sessions). I'll add sensors assessment (board and HDD temperatures) when I have a chance. The daemon decides if the machine should run or stop; it handles a red pill and a blue pill (flags raised in /var/lock/) that can skew its activity assessment towards keeping alive or sleeping. The machine can also wake-up from an RTC alarm, I have yet to integrate properly this mode. Reboot and Shutdown on-demand are also on the menu, these should be trivial to implement (and probably useless anyway.) The computer wakes-up from WOL (or alarm) when sleeping or down. As long as I don't use my Duet, that is ;) The deamon is queried by a client (via socket) which actually takes action. This lightweight client is launched by a (softy) real-time watchdog, ready to reboot the machine in case things go awry in the OS. Mixing ACPI suspend and a more or less RT watchdog took some doing but now it looks like its going to be solid. As I have paused server-side development, the current uptime counts in days, meaning many days of work (in music :) )/sleep cycles. Time will tell.
Let's come to Squeezebox management. Currently I miss the case of players listening to internet radio, and still connected to the local SqueezeCenter: network traffic on the server interface is just too low to record as meaningful activity. I would love to be able to query your plugin and get either an activity status for the components (squeezecenter, squeezeboxen) or a more synthetic active/idle indicator. I would love to be able to use your plugin's magic on suspend/shutdown/switch to SN (is there any other way to keep the clock to display, BTW ?) and maybe programmed alarms, if it can delegate the actual power actions (through idle status, red pill or blue pill ...) to that reboot-happy watchdog of mine. What do you think ? I know you've declared the plugin in RC, and congrats for that. In case your response is negative, I shall hack my ways around, no worries. But perhaps you'll be interested in emerging such a 2-way interface to other power management systems. I suppose that can be of interest when the server has more than one purpose. Once again: great job. PS: with currently 7 hard drives and capability to deliver tens of concurrent audio or video files on the network, the active machine rates 70-110W at the power plug, depending on disks activity, and 13W when suspended or shut down, so you see my point. When suspended it comes around in about 5 secs (I hope to go quicker than that), and TCP connections may still be alive. Cold boot time is not optimized either but I don't expect much less than 60-90 secs, and sadly minutes when hard drives check time has come. -- epoch1970 ------------------------------------------------------------------------ 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 [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
