-
Title
How to set a limit on the iolog -
Description
It is recommended that a limit is set on iologging to optimize performance. This option is not applied to a set of commands, rather it places a limit on how much of the data printed to the users screen between commands will be logged
-
Resolution
The iolog limit is set in pm.conf on the UPM master machine.
A simplified example of this would be if the limit is set to a very small size say 200 bytes "iolog_opmax=200;" and list a directory containing only a couple files then the optimization would not take effect as the output containing the directories contents would likely be under 200 bytes. If the same command is then used to list a directory containing ten files the amount of data printed to the screen would exceed 200 bytes and only the first few files would be logged. In this instance the I/O log would contain;
----------------------------------------------------
root@t1000:/tmp/test# ls -l
total 0
-rw-r--r-- 1 ixc ixc 0 2007-05-17 16:29 file1
-rw-r--r-- 1 ixc ixc 0 2007-05-17 16:30 file2
root@t1000:/tmp/test# ls -l
total 0
-rw-r--r-- 1 ixc ixc 0 2007-05-17 16:29 file1
-rw-r--r-- 1 ixc ixc 0 2007-05-17 16:30 file2
-rw-r--r-- 1 root root 0 2007-05-17 17:29 file3
-rw-r--...<<TRUNCATED>>
----------------------------------------------------
This option could be initially implemented for a single user to monitor the effect and help tune the amount of data being logged to an suitable level, eg iolog_opmax=8192 -
Additional Information
Related Links:
"How to enable keystroke logging":
https://support.quest.com/SUPPORT/index?page=solution&id=SOL355779