> From [EMAIL PROTECTED] Tue Dec 11 09:43:30 2001 > Date: Tue, 11 Dec 2001 09:36:16 -0700 > From: Daniel Carroll <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: LPRng: LPR bug? > > Hello, > > I'm having problems printing from HP's rlpdaemon to LPRng-3.7.9. > > The issue is that a user has batched up three files to send all at > once (the two extra files are "wrapped around" the actual data file > to be printed and contain HP LaserJet control codes), but the actual > data file to be sent is zero bytes in size.
RFC1179 states that 0 length files are actually 'read on the connection until closed'. This is really really really bad news. I suggest you install LPRng on the HP box. > > The result? The printjob gets stuck in limbo between the HP box and > LPRng. I'm guessing that I'm in a gray area of the RFC, but I'm not > certain. What I would like to know is if this is something that I > should be pestering HP about, and see if I can get them to not "spool" > zero-length printjobs? > > A few details: > Executing 'lpstat -ocompwork' on the HP-UX box returns (as the 1st 3 lines) > compwork-312 rcolby priority 0 Dec 6 12:12 on compwork > hpcps 46 bytes > diss.no 0 bytes > hpr 3 bytes > > The way the HP-UX box bundles this printjob up is with 3 df files > and one cf file. > > I have a tcpdump of the traffic exchange between the two servers, > and I can include it if anyone is interested, but the communication > essentially boils down to: > > HP->LPRng: \001 compwrk_prn1\n (extra space added for legibility) > LPRng->HP: \000 > HP->LPRng: \003 46 dA0312mesadm2\n (extra space added for legibility) > LPRng->HP: \000 > HP->LPRng: send 46 bytes of data > LPRng->HP: \000 > HP->LPRng: \000 > LPRng->HP: \000 > HP->LPRng: \003 0 dB0312mesadm2\n (extra space added for legibility) > LPRng->HP: \000 > HP->LPRng: \000 > > Then nothing more happens. I think the HP is expecting an "ack" from > LPRng at this point, but LPRng is still looking for a data file.... > > Thanks! > > - Dan > > ----------------------------------------------------------------------------- > 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. -----------------------------------------------------------------------------
