On Mon, Apr 12, 2004 at 08:45:11PM +0200, Christian Reiber wrote:
> Hello Patrick,
> 
> this is a reply to the thread "LPRng: HF_NAME information missing" in the 
> LPrng mailing list (the latest entry of that thread dates 
> Thu, 18 Mar 2004 23:15:58 -0800). Sorry that I send this mail directly to you,
> but it contains a solution which I do not want to release to the list before
> you have reviewed -- it is based on a more than vague knowledge what is going
> on, so I do not dare to publish it.
> 
> You proposed a patch and two list members reported that this patch does
> not solve the problem. I experienced the same in a setup a where a 
> FreeBSD client with a plain classic lpd prints to a remote print server
> which runs LPRng. 
> 
> I slightly changed the patch (for common/lpd_rcvjob.c) and now it works for me.
> I changed this line (line 435 in lpd_rcvjob.c):
> 
> ------
>         DEBUGF(DRECV2)("Receive_job: eof on transfer, job.info.count %d, files.count 
>         %d",
>                         job.info.count, files.count );
>                                 if( hold_fd ){
>                                         if( !discarding_large_job ){
> ------
>         DEBUGF(DRECV2)("Receive_job: eof on transfer, job.info.count %d, files.count 
>         %d",
>                         job.info.count, files.count );
> !                               if( hold_fd > 0){
>                                         if( !discarding_large_job ){
> ------
> 
> Traces showed that Check_for_missing_files() was called twice for this
> job, once from line 402 in lpd_rcvjob.c and a second time from line 439.
> I assume that this second call should not happen unless an hold file is
> allocated (so perhaps a "if (hold_fd != -1)" would even be better).
> 
> I now have no more printing delays when submitting a print job. (I just have 
> one of those [EMAIL PROTECTED] problems where the printer is locked up after the 
> first
> postscript job and unfortunately I have not yet discovered what it is missing;
> printing from a Windows box the same way works flawlessly, using tons of 
> driver code supplied by the vendor. So it must be something in the postscript
> which makes it hang :-(
> 
> In case you agree you will possibly want to post it on the list as a 
> follow-up to the mentioned thread (I am not a list member).
> 
> Cheers .... Christian
> 
> -- 
> Christian Reiber, [EMAIL PROTECTED]

This appears to be the case.

I will add the patch and repost it.

-- 
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 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.  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.
-----------------------------------------------------------------------------

Reply via email to