admsyslog(1M) DG/UX R4.11MU05 admsyslog(1M)
NAME
admsyslog - manage system error logging
SYNOPSIS
admsyslog -o add [ -f facility ] [ -l level ] action ...
admsyslog -o delete [ -f facility ] [ -l level ] [ action ... ]
admsyslog -o list [ -f facility ] [ -l level ]
admsyslog -o clean
admsyslog -o merge [ -qv ]
admsyslog -o report [ -qv ] [ -n nodes ] [ -i identifiers ] [ pattern
... ]
DESCRIPTION
admsyslog manages the system error logs maintained by syslogd(1M).
Syslogd directs error messages based on the facility that generated
the message, and the level of severity of the message. Messages can
be directed
- to a file.
- to a remote node.
- to one or more users, if the users are logged in.
- to all users logged in to the node generating the message.
Any message may be directed in more than one of the ways listed
above.
System error messages are sent to syslogd either by the kernel, by
the syslog(3C) library routine, or by the logger(1) command.
Operations
The following operations are supported.
add Add an entry to the system logging configuration file. The
entry provides one or more actions to take for messages
with a particular facility and level.
delete Delete an entry from the system logging configuration file.
list Display the current system logging configuration. This
includes the list of facility.level pairs which are being
logged, and the action to take for each type of message.
clean Clean up the /var/adm directory by renaming the messages
file and removing the oldest messages. This operation is
normally performed from a cron job. This operation should
not be used frequently, because error messages may be
discarded every time the operation is used.
merge Merge one or more reports into a single report, sorted by
date. This operation reads from standard input the output
of one or more invocations of the report operation. The
output format is the same as for the report operation.
report Generate a report of system errors that have been logged to
a file via syslogd. The report may be limited to messages
generated on certain nodes, or to messages containing
certain identifiers. The pattern, if used, further limits
the report to those messages which match the regular
expression, pattern.
Options
-f facility
Apply the operation to error messages from the facility.
The recognized values for facility are user, kern, mail,
daemon, auth, lpr, news, uucp, cron, mark, local0-7. See
syslog.conf(5) for a description of each facility. The
default value *, indicating all facilities.
-i identifiers
Report only messages produced by programs with an
identifier from the comma-separated list of identifiers.
The identifier for a command is usually the name of the
command. The identifier for DG/UX kernel error messages is
"dg/ux".
-l level Apply the operation to error messages of this level. The
recognized values for level are emerg, alert, crit, err,
warning, notice, info, debug, none. See syslog.conf(5) for
a description of each level. The default value for -o add
is info.
-n nodes Generate a report covering only those messages generated by
a node from the comma-separated list of nodes.
-q Use quiet mode. Do not include a header line for the
listing.
-v Use verbose mode. Include a header line for listings.
This is the default behavior.
EXAMPLES
To generate a report of all messages with the "statd" identifier:
admsyslog -o report -i statd
FILES
/etc/syslog.conf
Configuration file for syslogd.
/var/adm The default directory for system error messages.
OUTPUT
The list operation writes the facility, level, and action for each
selected type of message to standard output.
The report operation writes the date, node, facility, and text of
each selected message to standard output.
DIAGNOSTICS
Exit Codes
0 The operation was successful.
1 The operation was unsuccessful.
2 The operation failed due to access restrictions.
3 There was an error in the command line.
SEE ALSO
logger(1), syslogd(1M), syslog(3C), capdefaults(5) in the security
man pages, syslog.conf(5).
NOTES
You must have appropriate privilege to execute this command. For
systems supporting the DG/UX Capability Option, appropriate privilege
is defined as having one or more specific capabilities enabled in the
effective capability set of the user. See capdefaults(5) for the
default capabilities for this command. On systems without the DG/UX
Capability Option, appropriate privilege means that your process has
an effective UID of root. See appropriateprivilege(5) for more
information.
Licensed material--property of copyright holder(s)