Filter
Top Products
Printer Logging Through Logpaths
263
Printer Logging Through Logpaths
Destinations are logical queues with associated models and logpaths. Models
allow extra processing needed with the print jobs. Logpaths are used if
logging is desired for each job.
Each logpath on the NIC consists of two parts:
Type The type of log information to be captured. The choices are
job
for job ID and username,
user for user ID (and three messages
per job),
pgcnt for total pages printed in a job, cksum for file
checksums,
printer for special printer feedback, and ioport
for parallel printer status messages.
Port Where this log information will be sent to. The choices are a TCP
port number (e.g., 2000), an email address (including an alias),
or a central host running a SYSLOG daemon.
To view the current logpath settings on the print server, you can use either
Telnet or a Web browser as follows:
Telnet
Using Telnet, type the commands and your variable data as shown in the
example below:
Syntax:
list logpath
list logpath logpath
set logpath logpath port ioport
set logpath logpath type user job
save
Example:
10.221.1.25:root> list logpath
NAME LOG PORT LOG FLAGS
l1 - -
l2 - -
l3 - -
l4 - -
10.221.1.25:root> list logpath l2
log port:
log flags:
10.221.1.25:root> set logpath l2 port 9999
ok
10.221.1.25:root> set logpath l2 type user job
ok: user
ok: job
save