evlnotify(1)
NAME
evlnotify - Event Notification
SYNOPSIS
evlnotify -l | --list
evlnotify -a | --add notify-action [-o | --once-only]
[-f | --filter filter] [-p | --persistent] [-u | --uid
userid]
evlnotify -d | --delete notify-id ...
evlnotify -c | --change new-notify-action notify-id
evlnotify -F | --file cmd-file
DESCRIPTION
The evlnotify command lets you register actions to be
taken when a specified event occurs. An action (command or
shell script) will be executed on behalf of the user who
registered it, except if that user is root; root has the
option of specifying an alternate user id (other than
root).
The default environment settings are specified in
/etc/evlog.d/action_profile, which can be modified only by
root. The action command, or script, can alter its envi
ronment. The initial default is as follows:
PATH=/usr/bin:/bin:.
PWD=/tmp
A user attempting to issue the evlnotify command must have
access to at least one of the log files (/var/evlog/event_
log or /var/evlog/privatelog). In addition to verifying
that the user has read access to at least one of the log
files, an additional check is performed using a mechanism
similar to the crontab command:
- · If the file /etc/evlog.d/action.allow exists, then the
- users listed therein can issue this command.
- · Otherwise, if the file /etc/evlog.d/action.deny exists,
- but the action.allow file does not exist, then users listed in /etc/evlog.d/action.deny will not be allowed to issue the evlnotify command, and all others will be allowed to issue the command.
- · If neither the action.allow nor action.deny files exist,
- then all users can issue this command. Note that notifi
cations can only be modified or deleted by the users who
created them. - There are no command restrictions for root.
OPTIONS
Array(once-only=1 if once-only) (persistent=1 if persis
tent registration).
Array--persistent
EXAMPLES
ArrayThe fields are described above in the description
of the --list option. The first item in the list,
Notify ID 1, indicates that when an emergency event
is logged the /sbin/evlview command is executed
with options that will cause the event record to be
appended to the /tmp/emerg_log file. User ID is
root. Since the "once only" indicator is set to
'1,' this action will take place only once. The
persistent indicator is set to '1,' which indicates
that the registration is persistent, meaning that
is it read from the action_registry
(/etc/evlog.d/action_registry) and restored on
every boot-up.
Notify ID 2 indicates that when a critical event is
logged, /home/admin/testscript is executed. User
ID is joeusr.
FILES
- /var/evlog/eventlog
- Standard Event Log
- /var/evlog/privatelog
- Private Log
- /etc/evlog.d/action_registry
- Persistent Action Registry
- /etc/evlog.d/action_profile
- Default environment for notify_action
- /etc/evlog.d/action.allow
- Users allowed to register
- /etc/evlog.d/action.deny
- Users not allowed to register
SEE ALSO
- evlquery man page Filter expression syntax rules