10575, 10576, 10577, 10578, 10579, 10580
Tue Aug 29 10:20:36 MET DST 2000
psresolve papif tcpif holdif balanceif psif diskif
sol4 rs6000 sgi hppa alpha dg86 linux rhappc
interfaces could core dump while moving a job to error or hold queue
The interface programs could core dump in their finishing phase
where a completed print job is moved to a hold or error queue.
This happened under the rare circumstances that the lpd print
daemon accessed the queue lock file of the hold or error queue
at the same moment the printer interface did.
- In case a printer interface program could not access the
control files for the current print job anymore it did disable
the queue for printing. This did not make sense because a job
missing its control file can never printed again. Now the
affected print job will be thrown away.
- The printer interface programs could dump core while reading a
PPD file ending with a doublequote without closing quote.
- The no(tcp)resolve options of the "diskif" and "tcpif" did
cause unintended OpenImage processing overhead which is not
needed in case a print job isn't resolved.
- The printer interfaces which create files on EtherShare
volumes now remove the corresponding resource files, located
in the .rsrc directory properly in case the newly created
files have to be removed due to an error condition in the
- The printer interface programs "Extended print info" has
changed: In case a hi-res image is included by its EPSF layout
image the extended info will now look like: included '<UNIX
Pathname>' (<Reference Pathname>). The name of the EPSF
layout image has never been available at the moment the hi-res
file was included and therefore could never be mentioned in
the info text. The new syntax offers the possibility to
distinguish between a hi-res image included by a normal OPI
comment, in which case the old syntax '<Reference Pathname>'
replaced by '<UNIX Pathname>' is used and the case described
above. The syntax for all other type of layout images does not