Tell us what your trying to filter and I bet you¹ll get several versions of
an action routine from the list watchers that you can plug into PROP and it
will create/append to a log on the fly.
On 6/24/09 12:01 AM, Fred Schmidt fred.schm...@nt.gov.au wrote:
Neale Ferguson said...
Would it be
Neale Ferguson said...
Tell us what your trying to filter and I bet you¹ll get several
versions of an action routine from the list watchers that you can
plug into PROP and it will create/append to a log on the fly.
OK, here goes (userid's and IP addresses changed to protect the innocent)
Are you really after all the security violations? If so, an accounting
record is cut for every violation. The log messages (by default) will only
print after 3 or more attempts. Similarly, if you are after all
logon/logoff/disconnect/reconnect records an accounting record is cut for
these also. On
Neale Ferguson on Wed, 24 Jun 2009 17:32:14 -0700 wrote
* Are you really after all the security violations? If so, an
* accounting record is cut for every violation. The log messages
* (by default) will only print after 3 or more attempts.
* Similarly, if you are after
Is there a way of selecting all lines for a multi-line console log
message, rather than just the first?
We post-process the operator's console log files to look for Action
messages, writing them to a separate file. I use an XEDIT macro to do
this. However, we only get the first line of such
Hi Mike,
Yes, sorry. I should have given more details on the environment.
The console logs are from OPERATOR, processed by PROP to send them to
the Logical Operator, which uses the Performance Toolkit interface for
console management. The Performance Toolkit creates the log files that I
then
Would it be easier to create action routines for PROP so it will process the
messages as they come in rather than post-processing them when the format
may have changed?
Neale
