Patrick,
More data as I get more reports of this issue, in case it impacts where
you look in the code:
It can, in fact, happen without having to have been forwarded from one
server to another (though I do have a client entry in my printcap that
sends it to the printer at localhost, so maybe this is equivalent - see
a sample printcap entry below).
When this problem happens, the print job appears both on the printer of
the person who sent the job and on the incorrect printer _in place of
another print job_, i.e. person 1 sends a print job to printer 1 and
person 2 sends a print job to printer 2. The print job appears on
printer 1 just fine, but also turns up instead of what person 2 sent to
printer 2.
Printcap entry for two printers (the first is an AppleTalk, the second
an AppSocket) follows:
b120a|B120A:client:lpr_bounce:sd=/var/spool/lpd/b120a:lp=b120a@localhost
b120a|B120A:ab:bs=/usr/local/bin/lpbanner:server:tc=.print-test
b120b|B120B:tc=.print-test-ip
b120b|B120B:client:lpr_bounce:lp=b120b@localhost
b120b|B120B:server:sh:if=/usr/local/etc/filters/ifhp:lp=mm94385.mitre.org%9100
.print-test:\
lp=/var/spool/lpd/%P/null:\
sd=/var/spool/lpd/%P:\
if=/usr/local/etc/filters/ifmpap:\
of=/usr/local/etc/filters/ofmpap:\
connect_grace=10:\
chooser=/usr/local/eprint/bin/poll_printer.pl
.print-test-ip:\
sd=/var/spool/lpd/%P:\
chooser=/usr/local/eprint/bin/poll_printer.pl:\
connect_grace=10:\
network_connect_grace=10
--
Bill Knox
Senior Operating Systems Programmer/Analyst
The MITRE Corporation
[EMAIL PROTECTED] wrote:
>
> > From [EMAIL PROTECTED] Tue Sep 19 12:55:10 2000
> > Date: Tue, 19 Sep 2000 14:42:57 -0400
> > From: "William R. Knox" <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: Re: LPRng: Mystery Print Jobs Appearing
> >
> > Patrick,
> > Just to let you know, this is not the case with my problems. All queues
> > have separate spool directories. One thing which I have noticed is that
> > all of the jobs with which this happens APPEAR to be forwarded from one
> > print server to another, i.e.
> > job sent to server 1 via samba
> > server 1 sends job to server 2
> > server 2 prints job
> >
> > This follows the pattern reported by [EMAIL PROTECTED], who has a
> > single central print server and many remote ones. However, this may just
> > be a coincidence, as I have only three well documented/completely
> > trustworthy instances from which to draw. We do, however, have many jobs
> > that get sent directly from the server which initially receives the job
> > to the printer, and I haven't heard from them, so...
> >
> > I haven't gone digging into the code yet, but based on the debug output
> > at which I've looked, the datafile is opened in the parent lpd process
> > before forking off a child process to print it, such that the children
> > inherit all the open file descriptors. Is it possible that the child is
> > looking at the wrong open file to print? Is this a totally insane
> > theory? Am I desperately clutching at straws or what? I'm going to start
> > wading through the code and see what there is to see.
> > --
> > Bill Knox
> > Senior Operating Systems Programmer/Analyst
> > The MITRE Corporation
>
> This makes sense... I will look at the code.
>
> Patrick
>
> -----------------------------------------------------------------------------
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body. For the impatient,
> 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, send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> -----------------------------------------------------------------------------
-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
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, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
