Am Freitag, 9. Juni 2017 22:25:57 UTC+2 schrieb Ruediger Hahn: > Hi all, > > today I found out why our Windows clients don't enter sleep or hibernate > state any more. It is because bareos-fd is preventing these states: > > [code] > C:\WINDOWS\system32>powercfg -requests > DISPLAY: > None. > > SYSTEM: > [SERVICE] \Device\HarddiskVolume3\Program Files\Bareos\bareos-fd.exe > (Bareos-fd) > > AWAYMODE: > None. > > EXECUTION: > None. > > PERFBOOST: > None. > > ACTIVELOCKSCREEN: > None. > [/code] > > Does anybody know how to use the bareos-fd on windows without losing the > functionality of power saving modes?
Is no one else having this problem? I hope that Bareos is not being supported by electric supply companies :) Actually I'd really like to get a solution for this problem. As I mentioned: All Windows clients where the Bareos File Director software is installed don't get into sleep or any other power saving mode any more. If I enter the following command as and Administrator in a Windows 10 command line window: C:\powercfg -requests ...I get - among other lines - the following result: SYSTEM: [SERVICE] \Device\HarddiskVolume3\Program Files\Bareos\bareos-fd.exe (Bareos-fd) ...which probably means that it is the Bareos software preventing Windows from getting in any power saving mode. Before someone asks: This also happens when the client is inactive (the little icon is not blinking). Please help. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
