[ Bottom of Page | Previous Page | Next Page | Contents | Index | Library Home |
Legal |
Search ]
Commands Reference, Volume 1
chsensor Command
Purpose
Changes
the properties of
a resource monitoring and control (RMC) sensor.
Syntax
chsensor [-a | -n host1[,host2...]] [ -v | -V ] [-h]
name prop=value [prop=value]
Description
The chsensor command changes one or more properties of the sensor identified by name. If value is a string that contains spaces or other special
characters, it (value) must be enclosed in quotation marks. This
command returns the error messages and exit status of the underlying chrsrc resource monitoring and control (RMC) command.
The chsensor command runs on any node, including the management
server, and normally operates on the local node where it is run unless CT_CONTACT
is set. If you want chsensor to run on all of the nodes in a domain,
use the CT_MANAGEMENT_SCOPE environment variable. See the Environment variables section for more information.
See the mksensor command for a more complete explanation of RMC
sensors.
Flags
- -a
- Changes sensors that match the specified name on all nodes in the domain.
- -n host1[,host2...]
- Specifies the node on which the sensor should be changed. By default,
the sensor is changed on the local node. This flag is only appropriate in a management domain or a peer domain.
- -v | -V
- Writes the command's verbose messages to standard output. Use this flag to see the underlying
RMC command that is being run. This can help to interpret error messages that
are displayed.
- -h
- Writes the command's usage statement to standard output.
Parameters
- name
- Specifies the name of the sensor to be changed.
- prop=value
- Sets this sensor property to this new value.
Security
The user needs write permission for the IBM.Sensor resource class
in order to run chsensor. Permissions are specified in the access
control list (ACL) file on the contacted system. See the RSCT Guide and Reference for details on the ACL file and how to
modify it.
Exit Status
- 0
- The command has run successfully.
- 1
- An incorrect combination of and parameters has been entered.
- 6
- No resources were found.
If an error occurs in the RMC layer, the RMC return code will be returned
as the exit status.
Environment Variables
- CT_CONTACT
- When the CT_CONTACT environment variable is set to a host name
or IP address, the command contacts the resource monitoring and control (RMC)
daemon on the specified host. If this environment variable is not set, the
command contacts the RMC daemon on the local system where the command is being
run. The resource class or resources that are displayed or modified by the
command are located on the system to which the connection is established.
- CT_MANAGEMENT_SCOPE
- Determines the management scope used for the command's RMC daemon session.
The valid values are:
- 0
- Specifies local scope.
- 1
- Specifies local scope.
- 2
- Specifies peer domain scope.
- 3
- Specifies management domain scope.
If this environment variable is not set, local scope is used.
Examples
- To change the name of the NumLogins sensor to Numlog,
enter:
chsensor NumLogins Name=NumLog
Location
- /usr/sbin/rsct/bin/chsensor
- Contains the chsensor command
Related Information
Commands: chrsrc, lssensor, mksensor, rmsensor
Files: see the rmccli man page for information about prop=value syntax.
Books: see the RSCT Guide and Reference for information about the ACL authorization file and selection
string syntax.
[ Top of Page | Previous Page | Next Page | Contents | Index | Library Home |
Legal |
Search ]