Which option would you choose to activate logging on the global resource control facility to establish a syslog action on a resource control?

You have set resource controls on a project. Now you want to set up syslog to monitor a particular
resource control and log a message whenever the resource control is exceeded.
Which option would you choose to activate logging on the global resource control facility to
establish a syslog action on a resource control?

You have set resource controls on a project. Now you want to set up syslog to monitor a particular
resource control and log a message whenever the resource control is exceeded.
Which option would you choose to activate logging on the global resource control facility to
establish a syslog action on a resource control?

A.
Use the rctladm command to enable the global syslog attribute of a resource control.

B.
Use the prctl command to enable the global syslog attribute of resource control.

C.
Use the ipcs command to enable the global syslog attribute of a resource control.

D.
Use the setrctl command to enable the global syslog attribute of a resource control.

E.
By default, global logging of resource control violations is already enabled. Make an entry in the
syslog.conf file and refresh the system-log service.

Explanation:
Global Monitoring of Resource Control Events
Often, the resource consumption of processes is unknown. To get more information, try using the

global resource control actions that are available with the rctladm command. Use rctladm to
establish a syslog action on a resource control. Then, if any entity managed by that resource
control encounters a threshold value, a system message is logged at the configured logging level.



Leave a Reply 2

Your email address will not be published. Required fields are marked *


picoman

picoman

The answer should be A
root@solaris:~# rctladm -l
process.max-deferred-posts syslog=off [ lowerable deny count ]
process.max-sigqueue-size syslog=off [ lowerable deny count ]
process.max-itimers syslog=off [ deny count ]
process.max-port-events syslog=off [ deny count ]
process.max-msg-messages syslog=off [ deny count ]
process.max-msg-qbytes syslog=off [ deny bytes ]
process.max-sem-ops syslog=off [ deny count ]
process.max-sem-nsems syslog=off [ deny count ]
process.max-address-space syslog=off [ lowerable deny no-signal bytes ]
process.max-file-descriptor syslog=off [ lowerable deny count ]
process.max-core-size syslog=off [ lowerable deny no-signal bytes ]
process.max-stack-size syslog=off [ lowerable deny no-signal bytes ]
process.max-data-size syslog=off [ lowerable deny no-signal bytes ]
process.max-file-size syslog=off [ lowerable deny file-size bytes ]
process.max-cpu-time syslog=off [ lowerable no-deny cpu-time inf seconds ]
task.max-cpu-time syslog=off [ no-deny cpu-time no-obs inf seconds ]
task.max-processes syslog=off [ count ]
task.max-lwps syslog=off [ count ]
project.max-contracts syslog=off [ no-basic deny count ]
project.max-locked-memory syslog=off [ no-basic deny bytes ]
project.max-port-ids syslog=off [ no-basic deny count ]
project.max-shm-memory syslog=off [ no-basic deny bytes ]
project.max-shm-ids syslog=off [ no-basic deny count ]
project.max-msg-ids syslog=off [ no-basic deny count ]
project.max-sem-ids syslog=off [ no-basic deny count ]
project.max-crypto-memory syslog=off [ no-basic deny bytes ]
project.max-tasks syslog=off [ no-basic count ]
project.max-processes syslog=off [ no-basic count ]
project.max-lwps syslog=off [ no-basic count ]
project.cpu-cap syslog=n/a [ no-basic deny no-signal inf no-syslog count ]
project.cpu-shares syslog=n/a [ no-basic no-deny no-signal no-syslog count ]
zone.max-lofi syslog=off [ no-basic deny count ]
zone.max-swap syslog=off [ no-basic deny bytes ]
zone.max-locked-memory syslog=off [ no-basic deny bytes ]
zone.max-shm-memory syslog=off [ no-basic deny bytes ]
zone.max-shm-ids syslog=off [ no-basic deny count ]
zone.max-sem-ids syslog=off [ no-basic deny count ]
zone.max-msg-ids syslog=off [ no-basic deny count ]
zone.max-processes syslog=off [ no-basic count ]
zone.max-lwps syslog=off [ no-basic count ]
zone.cpu-cap syslog=n/a [ no-basic deny no-signal inf no-syslog count ]
zone.cpu-shares syslog=n/a [ no-basic no-deny no-signal no-syslog count ]

tb

tb

A.

Global Actions on Resource Control Values

Global actions apply to resource control values for every resource control on the system. You can use the rctladm command described in the rctladm(1M) man page to perform the following actions:

Display the global state of active system resource controls

Set global logging actions

You can disable or enable the global logging action on resource controls. You can set the syslog action to a specific degree by assigning a severity level, syslog=level. The possible settings for level are as follows:

debug

info

notice

warning

err

crit

alert

emerg

By default, there is no global logging of resource control violations. In the Solaris 10 5/08 release, the level n/a was added for resource controls on which no global action can be configured.