Default Parameters for RPiClockFreqTest

This test reports the current clock frequency of the Raspberry Pi and alerts administrators, if abnormalities are detected.

This page depicts the default parameters that need to be configured for the RPiClockFreqTest test.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• The USE SUDO parameter applies only to Linux and Solaris systems. By default, the USE SUDO parameter is set to No. This indicates that, by default, this test will report metrics by executing the df -Pk –l command on the Solaris host. However, in some highly secure environments, the eG agent install user may not have the permissions to execute this command directly. In such cases, do the following:

• Edit the SUDOERS file on the target host and append an entry of the following format to it:

  <eG_agent_install_user> ALL=(ALL) NOPASSWD: <Command>

  For instance, if the eG agent install user is eguser, then the entry in the SUDOERS file should be:

  eguser ALL=(ALL) NOPASSWD: df –Pk -l

• Finally, save the file.

• Then, when configuring the test using the eG admin interface, set the USE SUDO parameter to Yes. This will enable the eG agent to execute the sudo df –Pk –l command and retrieve the desired metrics.

• This parameter is relevant only when the USE SUDO parameter is set to ‘Yes’. By default, the SUDO PATH is set to none. This implies that the sudo command is in its default location - i.e., in the /usr/bin or /usr/sbin folder of the target Solaris host. In this case, the eG agent automatically runs the df -Pk –l command with sudo from its default location, once the USE SUDO flag is set to Yes. However, if the sudo command is available in a different location in your environment, you will have to explicitly specify the full path to the sudo command in the SUDO PATH text box to enable the eG agent to run the sudo command.

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.