done_jobs_max_age=NRemove status when older than N
seconds
send_failure_action=Action on Failure
sendmail=sendmail path name and options
stop_on_abort FLAG Stop processing queue on filter abort
If the job processing terminates abnormally, the following
sequence of events occurs:
The job is marked as having an error during
processing.
The lpd server will attempt
to kill all filters and other associated processes by
sending a SIGINT and SIGCONT (kill
-INT and kill -CONT) to
them.
If there is a mail_operator_on_error value, the
specified operator will be mailed an error indication.
The sendmail option specifies
the pathname of the sendmail
program and the options needed to have it read mail
addresses from its standard input. For example, sendmail=/usr/sbin/sendmail -oi -t
is a commonly used set of options.
The mail_from value specifies
the user name used for mail origination. If not
specified, the default is to use the print spool queue or
printer name.
If there is a send_failure_action specified, then it is
decoded and the corresponding action taken. If the value
is remove, hold, abort, or
retry, then the job is removed,
held, aborted, or retried. If the value is |/program, the program is executed and
the number of attempts are written to the filter STDIN. The exit status of the
filter will be used to determine the consequent actions.
That is, JSUCC (0) will be success, and the standard
success action will be taken; JFAIL will cause retry,
JREMOVE will cause the job to be removed, JHOLD will
cause the job to be held, JABORT or other status will
abort processing.
If the status is ABORT and the stop_on_abort flag is set, then further
processing of jobs is terminated. The job is not removed
from the queue.
If the error status indicates removal, the save_on_error flag is clear, and the done_jobs and done_jobs_max_age values are zero (0),
then the job is removed from the spool queue.
If the error status indicates that no further
operations should be performed on the queue, then the lpd server will stop processing
jobs.
If the error code indicated that the job should be
retried, and the send_try value
is 0 or the number of attempts is less than the send_try value, then the job is
retried. Between each attempt to transfer a job to a
remote site. This pause will double after each attempt,
reaching a maximum of max_connect_interval seconds. If max_connect_interval is 0, there is
no limit on the interval value.