From [EMAIL PROTECTED] Mon Jul 26 14:12:10 2004
Subject: LPRng: Bug and question with incoming_control_filter and
append_z
(3.8.27)
Date: Sat, 24 Jul 2004 12:33:52 -0400
From: Daniel Sharpe [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
I recently upgraded from version 3.8.20 to version 3.8.27 and it
appears
that if my incoming_control_filter modifies the Z line that the
additional options giving in append_z or prefix_z are never added to
the
Z line that lands in the hfA control file. I don't have a system w/
3.8.20 to test whether the options were added prior to calling the
control_filter or after.
An easy work around is to add them in the filter itself from the
PRINTCAP_ENTRY environment variable.
Also, in the documentation for the new incoming_control_filter in the
release notes there is a strong warning against mucking with the
contents of the A line. Can someone with more background provide more
details about the 'risks' of changing this line? Is it safe to change
the user and host info as long as the job number itself is not
touched?
Thanks for any help,
--Daniel
The append_z and prefix_z actions are done BEFORE the
incoming_control_filter.
The incoming_control_filter will then process/replace the line with new
or modified values.
The incoming_control_filter is the last action that is performed before
the
job data and control files are written to the spool queue.
The 'A' information is the 'job identifier'. This is (hopefully)
a unique identifier for the job, and consists of the
[EMAIL PROTECTED]
Changing this value will have, I think, after looking at the code, no
effect
on anything used/done by LPRng, but may have side effects on other
parts of your system that use the job identifier. Which appear to be
simply to report its value in the various status fields.
You can change the 'user' and 'host' information in the
incoming_control_filter, but you should be aware that these values
may be used for authentication in other parts of the printing system.
At the point where the incoming_control_filter modifies them they
are no longer used or checked during the incoming job processing.
Note that this information is not used to generate a new 'job
identifier',
so you will have to change that as well.
In the next release, if you are feeling REALLY agressive, you can
even change the contents of the job data files. You can even remove
them. After running the incoming_control_filter, LPD will check to
see if the files are still present and if not, remove then from the
job file list.
Patrick
Patrick Powell Astart Technologies
[EMAIL PROTECTED]6741 Convoy Court
Network and System San Diego, CA 92111
Consulting 858-874-6543 FAX 858-751-2435
LPRng - Print Spooler (http://www.lprng.com)
-
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRng MAILING LIST
The address you post from or your Reply-To address MUST be your
subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.
To subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST mailaddr | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST mailaddr | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, call Patrick Powell or one of the friendly
staff at Astart Technologies for help. Astart also does support for LPRng.
Also, check the Web Page at: http://www.lprng.com for any announcements.
Astart Technologies (LPRng - Print Spooler http://www.lprng.com)
6741 Convoy Court
San Diego, CA 92111
858-874-6543 FAX 858-751-2435
-
