home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
PowerScheduler plugin -- Standby timeout timer does not get update
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1194124" data-attributes="member: 82144"><p>Edward,</p><p></p><p>You seem to expect PowerScheduler to completely manage the system power. Actually, Windows is responsible for automatically suspending (standby, hibernate, shutdown) the system. PowerScheduler's main purpose is only to prevent automatic suspension in certain scenarios (eg. network activity). It's very important that you understand that clearly.</p><p></p><p></p><p>Windows is responsible for recognising all regular system user activity - including terminal service log in - and delaying/preventing automatic suspension. PowerScheduler doesn't have to do anything, so that's why that activity isn't tracked.</p><p></p><p></p><p>The correct understanding is: PS prevents Windows from suspending the server when there is network traffic.</p><p></p><p></p><p>The correct understanding is: PS prevents Windows from suspending the machine for X minutes after the last <strong>MediaPortal user activity</strong>.</p><p></p><p></p><p>You are mistaken. MediaPortal user activity (eg. going to a different section within MediaPortal, playing media within MediaPortal) is the only valid condition related to the timeout setting. Network traffic, file shares, processes etc. are not MediaPortal user activity, so they are not valid conditions. </p><p></p><p>As explained above: system activity such as terminal service log in/out is not valid MediaPortal user activity. PowerScheduler doesn't have to detect or handle that activity because Windows already detects and handles it.</p><p></p><p></p><p>I think you may have created this problem for yourself when you enabled the force-standby-when-idle setting:</p><p>[2016-08-23 07:59:23,094] [Log ] [TVService] [DEBUG] - PS: PowerScheduler forces system to go to standby when idle: True</p><p></p><p><a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/13_Plugins/Power_Scheduler/2_Server_Configuration#PowerScheduler_forces_system_to_go_to_standby_when_idle" target="_blank">http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/13_Plugins/Power_Scheduler/2_Server_Configuration#PowerScheduler_forces_system_to_go_to_standby_when_idle</a></p><p></p><p>As far as I can see, that setting is the reason why you only get the 2 minute grace period.</p><p></p><p>Why did you enable that setting?</p><p></p><p>Regards,</p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1194124, member: 82144"] Edward, You seem to expect PowerScheduler to completely manage the system power. Actually, Windows is responsible for automatically suspending (standby, hibernate, shutdown) the system. PowerScheduler's main purpose is only to prevent automatic suspension in certain scenarios (eg. network activity). It's very important that you understand that clearly. Windows is responsible for recognising all regular system user activity - including terminal service log in - and delaying/preventing automatic suspension. PowerScheduler doesn't have to do anything, so that's why that activity isn't tracked. The correct understanding is: PS prevents Windows from suspending the server when there is network traffic. The correct understanding is: PS prevents Windows from suspending the machine for X minutes after the last [B]MediaPortal user activity[/B]. You are mistaken. MediaPortal user activity (eg. going to a different section within MediaPortal, playing media within MediaPortal) is the only valid condition related to the timeout setting. Network traffic, file shares, processes etc. are not MediaPortal user activity, so they are not valid conditions. As explained above: system activity such as terminal service log in/out is not valid MediaPortal user activity. PowerScheduler doesn't have to detect or handle that activity because Windows already detects and handles it. I think you may have created this problem for yourself when you enabled the force-standby-when-idle setting: [2016-08-23 07:59:23,094] [Log ] [TVService] [DEBUG] - PS: PowerScheduler forces system to go to standby when idle: True [URL]http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/13_Plugins/Power_Scheduler/2_Server_Configuration#PowerScheduler_forces_system_to_go_to_standby_when_idle[/URL] As far as I can see, that setting is the reason why you only get the 2 minute grace period. Why did you enable that setting? Regards, mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
PowerScheduler plugin -- Standby timeout timer does not get update
Contact us
RSS
Top
Bottom
