Just to confirm, something similar has been happening to us with
ifhp-3.2.21 and Phaser 740. For some reason 6 copies of the same
print job were created on the printer. Downgrading to ifhp-3.2.19 solved
the problem.
Ralf
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 22, 2000 2:07 PM
To: [EMAIL PROTECTED]
Subject: Re: LPRng: Mystery Print Jobs Appearing
> 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.
-----------------------------------------------------------------------------
