Filter
Top Products
Syntax Used in VPO Configuration Files
Pattern Matching
Appendix A298
Pattern Matching Examples
Table A-3 Pattern Matching Examples
Format Recognized Messages
Error Will recognize any message containing the
keyword “Error” at any place in the message.
panic Matches all messages containing “panic”, “Panic”,
“PANIC”, etc., at any place, if case insensitive
mode is used.
logon|logoff Recognizes any message containing the keyword
“logon” or “logoff”.
ˆgetty:
<*.msg> errno<*><#.errnum>$
Matches messages of format: “getty: cannot open
tty’xx’ errno : 6” or “getty: can’t open ttyop3; errno
16” Note: the anchoring symbol $ is used to assign
the number at the end of the input line to
errnum.
ˆerrno[ |=]<#.errnum> <*.errtext> Matches messages of format: “errno 6 - no such
device or address” as well as “errno=12 Not enough
core” The space between <#.errnum> and
<*.errtext> is used as delimiter for correct
assignment of the number to errno.
ˆhugo:<*>:<*.uid>: Matches any entry in /etc/passwd for user ‘hugo’
and returns the user ID in parameter uid. Note
the “:” at the end of the pattern to delimit uid from
the succeeding group ID in the input pattern.
ˆWarning: <*.text> on node
<@.node>$
Matches a message of format “Warning: too many
users on node hpbbx” and assigns “too many users”
to text and “hpbbx” to node. Note: the anchoring
symbol $ is used to assign the word at the end of
the input line to node.
SU<*>+<@.tty>
<![root|admin].from> -<*.to>
Matches all SU logfile entries of all users except
for “root” and “admin”.