Valid on UNIX
The secons utility displays CA ControlMinder run-time statistics about system behavior including:
This command has the following format:
secons -i
Displays runtime statistics as formatted text.
Example: Display run-time data
The following example shows the output of the secons -i command:
Runtime Statistics: ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ INet statistics: Requests denied : 0 Requests granted : 17 Errors found : 0 Queues size: Audit log: 0 Error log: 0 Cached tables info: ACEE handles : 11 Protected clients : 0 Trusted programs : 77 Untrusted programs: 3 Database info: (Record count & first free ID) Classes : 235 ( CID 0x00f0 ) Properties : 4829 ( PID 0x1346 ) Objects : 842 ( OID 0x0000035a ) PropVals : 4109 ( N/A )
CA Access Control memory utilization statistics: ----------------------------------------------- CA Access Control security daemon (seosd, pid=4265 Total=13MB Res=8MB) CA Access Control agent daemon (seagent, pid=4268 Total=10MB Res=3MB) CA Access Control watchdog daemon (seoswd, pid=4276 Total=6MB Res=3MB) CA Access Control policyfetcher daemon (policyfetcher, pid=4331 Total=11MB Res=1MB) CA Access Control AgentManager daemon (AgentManager, pid=4561 Total=22MB Res=3MB)
Kernel load statistic: Queue: ----- FILE: SEOS current queue depth : 0 SEOS max queue depth : 1 SEOS current queue rate : 0 req/msec SEOS max queue rate : 0 req/msec SURROGATE: SEOS current queue depth : 0 SEOS max queue depth : 1 SEOS current queue rate : 0 req/msec SEOS max queue rate : 0 req/msec Total: SEOS current queue depth : 0 SEOS max queue depth : 2 SEOS current queue rate : 0 req/msec SEOS max queue rate : 20 req/msec Syscalls: ------- FILE: Active SEOS handlers : 0 syscs SEOS hanlers calling rate : 0.086678 sysc/msec(406 handlers within 4684 msecs) Average processing time : 0.014742 msecs (407 handlers within 6 msecs) SURROGATE: Active SEOS handlers : 0 syscs SEOS hanlers calling rate : 0.000043 sysc/msec(363 handlers within 8368826 msecs) Average processing time : 0.126374 msecs (364 handlers within 46 msecs) ----------------------
The following explains each line in the preceding output:
INet statistics: Requests denied : 0 Requests granted : 17 Errors found : 0
Displays statistics of network access authorization performed by CA ControlMinder. These lines summarize the number of denials, grants, and errors during the authorization of network requests.
Queues size: Audit log: 0 Error log: 0
Since CA ControlMinder creates logging with file locking, it is possible that certain events are held in memory and written to log files after a while. If these values exceed 10, then an error could be interfering with the CA ControlMinder logging facility.
Cached tables info: ACEE handles : 11 Protected clients : 0 Trusted programs : 77 Untrusted programs: 3
Displays information about the size of cached tables CA ControlMinder uses:
Database info: (Record count & first free ID) Classes : 235 ( CID 0x00f0 ) Properties : 4829 ( PID 0x1346 ) Objects : 842 ( OID 0x0000035a ) PropVals : 4109 ( N/A )
General information regarding the size of the database and the number of records in each part of the database.
Displays information about the size of the memory the following daemons use: seosd, seagent, seoswd, policyfetcher and AgentManager:
CA Access Control memory utilization statistics: ----------------------------------------------- CA Access Control security daemon (seosd, pid=4265 Total=13MB Res=8MB) CA Access Control agent daemon (seagent, pid=4268 Total=10MB Res=3MB) CA Access Control watchdog daemon (seoswd, pid=4276 Total=6MB Res=3MB) CA Access Control policyfetcher daemon (policyfetcher, pid=4331 Total=11MB Res=1MB) CA Access Control AgentManager daemon (AgentManager, pid=4561 Total=22MB Res=3MB)
The CA ControlMinder watchdog daemon monitors the memory use of the daemons based on the interval defined in the ProcVSizeInterval token. If a process exceeds the specified watermark in the ProcVSizeHigh token, the watchdog restarts the process within the time frame defined in the ProcRestartHours token. If a process exceeds the memory size specified in the ProcVSizeCritical token, the watchdog daemon immediately restarts the process.
Copyright © 2013 CA Technologies.
All rights reserved.
|
|