Make sure that you set the network timeout on the printer to
something pretty large as well.
Ummm... you did update the JetDirect flash, didn't you?
Patrick
> From [EMAIL PROTECTED] Wed Feb 28 10:50:31 2001
> From: Dave Lovelace <[EMAIL PROTECTED]>
> Subject: LPRng: missing end of job
> To: [EMAIL PROTECTED]
> Date: Wed, 28 Feb 2001 12:27:09 -0500 (EST)
>
> Hi. I've got a problem.
>
> We're running LPRng 3.6.24 and ifhp 3.3.17 under RedHat 6.2. This machine
> is not acting as a print server for anyone else, so not that many jobs
> have been over a few pages. A few times in the past I'd seen this, but
> never followed up on it. Now I've got a case where things seem to be
> quite consistent.
>
> All printing is via appsocket to an HP 4+ (to the JetDirect's port
> 9100). This printer is also used by another Unix box on the same
> network (using SYSV lp/lpsched system); from there, we are not seeing
> anything like this. Most printing is from that host, including a fair
> number of really large jobs, so I'm reasonably sure that the printer &
> JetDirect box are not to blame.
>
> The problem is that on large-ish jobs the end of the job appears to just
> vanish. For what it's worth, the printer's LED display is left showing the
> username of the user who queued up the job, so whatever cleanup is supposed
> to be done to set that back to "Ready" is not happening, either. (However,
> the (partial) last page is being ejected, for what *that*'s worth.)
>
> Now, I had occasion to print this report. It got through most of 14 pages
> & stopped. (The queue showed the job as finished; I'm not going to mention
> it again, but it's the case each time.) I needed to make some minor changes,
> so I did so & printed again. The same result, though not stopping at exactly
> the same point. I jumped to the conclusion that my changes caused the
> difference in where printing stopped, so I printed the exact same report
> again. This time it got through most of 15 pages before stopping.
>
> Now, so far the printing was being done using a pipeline into lpr (several
> previous processes, in sequence, generating the report). I wondered whether
> it was possible that one of the programs generating it was to blame, so
> I ran them with output to a file instead of into lpr. The entire thing
> was there. (The report is text, with some PCL commands prepended to set
> the printer the way it's wanted, so this is easy to see.)
>
> At this point I thought I'd try printing the file, in case the pipeline
> was somehow to blame. It stopped after almost 15 pages, in the middle
> of a word - not at the same place as before. However, I tried printing
> this file twice more, and each time it stopped at exactly the same place.
> Since it kindly stopped in the middle of a word, I can say with certainty
> that exactly 37960 bytes' worth of it make it to the printer.
>
> In the middle of this I read the HOWTO some more, and wondered if adding
> a socket_linger setting would make a difference. It did not. (But if
> you wonder what it's doing in there, that's why it's there.)
>
> Here is the printcap entry for the printer in question:
>
> laser:\
> :sd=/var/spool/lpd/laser:\
> :mx#0:\
> :mc#0:\
> :socket_linger#90:\
> :sh:\
> :lp=laser%9100:\
> :ifhp=model=hp4plus,status@:\
> :if=/usr/local/libexec/filters/ifhp -Z land66hp:
>
> (The "-Z land66hp" causes the initial PCL commands to be inserted. Not
> much other change in ifhp's configuration.)
>
> If anyone can tell me how to fix this problem, I'd really appreciate it.
> Testing at 15 pages per test is getting my boss jumpy about the paper being
> wasted, BTW.
>
> --
> - Dave Lovelace
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
> -----------------------------------------------------------------------------
> 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.
> -----------------------------------------------------------------------------
>
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
