Reply to thread

Message

MM,

I have a LSI hardware RAID card in the server in order to hold all the media content and it doesn't like any sleep/standby state except complete shutdown and restart. That's why I have to set powerscheduler to force S5. If powerscheduler is designed to only reset the timeout by user activity (i.e. more for client side usage which I can understand), that's fine. I can workaround with setting the ping monitor to look at the client machines so to keep the server alive although that would not give maxmium power saving as I can be using the client for activites not involving the server.

Just another thought. Is it possible to make the 2 minutes grace period configurable? That can also work without conflicting with the usage of the _lastUserTime variable.

In any case, I like the powerscheduler. It's a very powerful tool.

Regards,

Edward

<blockquote data-quote="Edward Cheung" data-source="post: 1194126" data-attributes="member: 159714">MM,I have a LSI hardware RAID card in the server in order to hold all the media content and it doesn't like any sleep/standby state except complete shutdown and restart. That's why I have to set powerscheduler to force S5. If powerscheduler is designed to only reset the timeout by user activity (i.e. more for client side usage which I can understand), that's fine. I can workaround with setting the ping monitor to look at the client machines so to keep the server alive although that would not give maxmium power saving as I can be using the client for activites not involving the server.Just another thought. Is it possible to make the 2 minutes grace period configurable? That can also work without conflicting with the usage of the _lastUserTime variable.In any case, I like the powerscheduler. It's a very powerful tool.Regards,Edward</blockquote>

[QUOTE="Edward Cheung, post: 1194126, member: 159714"] MM, I have a LSI hardware RAID card in the server in order to hold all the media content and it doesn't like any sleep/standby state except complete shutdown and restart. That's why I have to set powerscheduler to force S5. If powerscheduler is designed to only reset the timeout by user activity (i.e. more for client side usage which I can understand), that's fine. I can workaround with setting the ping monitor to look at the client machines so to keep the server alive although that would not give maxmium power saving as I can be using the client for activites not involving the server. Just another thought. Is it possible to make the 2 minutes grace period configurable? That can also work without conflicting with the usage of the _lastUserTime variable. In any case, I like the powerscheduler. It's a very powerful tool. Regards, Edward [/QUOTE]