JJZolx;626080 Wrote: > Something tells me that if you tried to do this it would only block the > server from being able to do anything for that same amount of time. In > the end it probably wouldn't really make a difference, but if you're > waiting for the server to come up, it could be even more annoying. Not annoying in my case, as it will run automatically at 2:15 am. My server spends most of its life in S3 sleep when it's not actively playing. When it does boot (or reboot), it's generally in those wee hours.
Additionally, that "seed" query only partially blocks. I just tested this with a playlist pre-loaded for my transporter. I rebooted the server and as soon as SBS was stared, I was able to start playing that playlist. The playlist continued to play while the "tracks 0 500 new" query was fired off in the background. True, I couldn't change tracks for those 46 seconds, but the the player continued playing...probably due to buffering in the transporter. Since SrvrPowerCtrl defaults to waking the server up 5 minutes before alarms, even if it's waking from a cold shutdown, the "seed" query should be done in plenty of time so that it won't interfere with the alarm. So, on balance, I'm thinking that the seed query is less annoying for me than the regular SBS behavior I'm seeing. I'm not suggesting that my solution here is anything more than an ugly kludge. It will solve the problem for me, though. -- gharris999 ------------------------------------------------------------------------ gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115 View this thread: http://forums.slimdevices.com/showthread.php?t=87070 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
