We had a similar problem with very large jobs. We found that the socket
connection to the printer was timing out before the job finished. We were able
to solve it by extending or disabling send_job_rw_timeout. We did this in the
lpd.conf on the clients. I imagine you can also set it in the printcap,
although I've never tried.
We also have seen the same symptoms with larger jobs to printers for which
status is disabled. Check and make sure that status is turned on in ifhp.conf
(it should be by default).
-Greg
On Tue, 3 Jul 2001, Dave Lovelace wrote:
> I posted about this a while back, and I don't think anyone responded.
> We're to a point where it's getting to be a *really* big problem, and I
> have no idea what to do.
>
> We're running LPRng 3.6.24 on RedHat 6.2, and our printer is
> HP Laserjet 4 Plus. (We're using ifhp (3.3.17?), but for reasons given
> below I'm fairly sure that the problem occurs after ifhp is done.
> The printer has an external JetDirect box, and we print to port 9100.
>
> We also print to this printer from a SysV Unix box, using the lpsched
> system that came with it (but again printing to port 9100), and we do
> not see this problem at all with it, ever.
>
> The problem is that we lose the ends of jobs of more than a few pages.
> The printout just stops at some point, usually in the middle of a page.
> If the same job is sent again, it stops at exactly the same point.
> Or at least it has done so in a number of tests.
>
> Whenever this happens, the status readout on the printer is left showing
> the username of the user who sent the job. This would appear to indicate
> that the PJL commands to reset it are part of what's lost - which seems
> reasonable on the face of it, after all.
>
> In reading the HOWTOs, the only thing I could find that looked remotely
> like it might relate was the socket_linger parameter. I've tried
> boosting it way up there, with no change whatever.
>
> I've set up a printer exactly the same except printing to file. I can
> see that everything is there - stuff at the beginning added by ifhp,
> the file being printed, and PJL commands at the end. If I move this
> whole thing to the SysV box and send it (binary mode) to the printer,
> the whole thing prints. It sure looks as though LPRng is the culprit.
>
> Here's the printcap entry for the printer. (The "-Z land66hp" causes
> ifhp to add some extra setup stuff at the beginning of the job. It
> works fine for shorter jobs.)
>
> 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:
>
> As I say, I've tried boosting the socket_linger up much higher, with
> no result whatever.
>
> As we're now setting things up so that this box is our print server
> for all our PCs, this is very quickly going to be a solve-it-or-die
> problem for me. I have no idea whatever to do about it. If anyone
> sees anything I might be missing, please speak up quickly.
> (And I sure hope Patrick is listening at this point.)
>
> Thanks. <sigh sigh sigh sigh sigh>
>
>
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
