Oh yea. Been there... It uses 2% of an IFL by default. Not so great when you have many many servers
This is from IBM on how to tame it. Basically you need to tell it you are a laptop that needs to go to sleep :) The settings go on the bigfix master, not the client end. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- the BigFix client continuously checks the compliance status of an endpoint. For this reason it uses the configured amount of CPU (2% by default) for performing this activity, that is a continuous checking cycle. Customers using only SUA could not be interested in this continuous monitoring: they can thus have the agent execute a checking cycle, then sleep for some time, then wake up and execute another cycle and so on. The sleeping is controlled by few settings: _BESClient_Resource_PowerSaveEnable _BESClient_Resource_PowerSaveTimeout0 _BESClient_Resource_PowerSaveTimeout1 _BESClient_Resource_PowerSaveTimeout2 _BESClient_Resource_PowerSaveTimeout3 _BESClient_Resource_PowerSaveTimeout4 _BESClient_Resource_PowerSaveTimeout5 They are explained in: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/Configuration%20Settings An interesting discussion about their usage is on our forum at: https://forum.bigfix.com/t/automatically-adjust-besclient-settings-when-on-battery-power/12962 Setting _BESClient_Resource_PowerSaveEnable to 1 and _BESClient_Resource_PowerSaveTimeout0 to 30 should force the client to completely sleep for 30 minutes between each compliance check cycle. -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Victor Echavarry Sent: Tuesday, February 27, 2018 5:47 AM To: [email protected] Subject: [LINUX-390] BESCLIENT A couple of days ago our VM's begin a sustained increase in CPU usage. We began an investigation checking recently changes on the LPAR's and the guests. The only thing we found is that inside all the guests the BESCLIENT was installed. Although it the process doesn't show high CPU utilization, we turn it off and the VM's stabilized. Do anyone has similar issue with this product? Regards, Victor Echavarry System Programmer Operating Systems EVERTEC, LLC ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
