Config Logging Command - impinj RShell Reference Manual

RShell Reference Manual
If the reader is in auto mode during the execution of this command, it is possible that the reader
is currently retrieving the metafile or performing an upgrade. In these instances, this command
may return "Previous-Command-In-Progress."
Note that this command does not change the reader's upgrade configuration URI, but it sets the
retrieve-mode to manual, meaning that the reader will not periodically retrieve the upgrade
configuration metafile until the retrieve-mode is set to auto again.
4.2.3

Config Logging Command

The commands provide configuration options for the storage and forwarding of
config logging
logged events. Logged events are forwarded using the standard Syslog protocol to a remote
Syslog server. Internally the logged events are stored in the reader's filesystem, accumulating
and persisting across reboots. All logged events have an associated severity level, only events of
severity greater than or equal to the user configured level are retained. Logs are classified into
management, rfid and system categories.
The user log severity may be set to one of eight levels (in decreasing order from most severe to
least severe): emergency, alert, critical, error, warning, notice, info, and debug. For example if
the log level is set to alert, then only logs classified as emergency or alert will be processed.
Regardless of how the user configures the log settings, all error (and higher severity) logs in all
categories are retained in an error log independent of the user controlled 'application' log.
Figure 4-1 illustrates a configuration where the reader management category of logs set to
critical (and above), the RFID related logs set to warning (and above) and lastly the system logs
set to alert (and above).
Proprietary and Confidential 11
Revision 4.2, Copyright © 2009, Impinj, Inc.