This actually never worked for me, with versions of LPRng back to early 3.7.
If I ever used LPRng with ifhp and wanted accounting (like I told that other guy about a month ago and this solved his problem), I needed to make lp=/dev/null and tell ifhp=dev=printer%9100 instead. It seems that LPRng does not pass the lp line to ifhp or something like that. As far as I know, though, this is nothing new. I'd suggest the person try it this way and see what happens -- maybe they're just mistaken about the way they've been doing things. <shrug> ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin |$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 732/235.4473 (5-4473) \__/ Univ. of Med. and Dent. | IST/ACS - Robert Wood Johnson MS - S-B11 On Mon, 17 Dec 2001, Patrick Powell wrote: > Hmmm... I tried this with ifhp-3.5.0 and did not have this > problem... I wonder what is happening here. > > By the way, I may soon have bidirectional parallel port stuff > working... but you will have to update to the latest parport set of > patches that have implemented non-blocking reads correctly. > > Patrick > > > From [EMAIL PROTECTED] Tue Dec 11 14:52:38 2001 > > Date: Wed, 12 Dec 2001 08:45:08 +1100 > > To: [EMAIL PROTECTED] > > Subject: LPRng: [[EMAIL PROTECTED]: Bug#123348: lprng & ifhp no longer >want to play nice - kinda] > > From: [EMAIL PROTECTED] (Craig Small) > > > > This is a bug report I have recieved from a Debian user. I suspect there > > may be some interaction between the two programs that is different now. > > I have also attached his next message that has an update. > > > > ----- Forwarded message from Jamie Heilman <[EMAIL PROTECTED]> ----- > > > > Subject: Bug#123348: lprng & ifhp no longer want to play nice - kinda > > Reply-To: Jamie Heilman <[EMAIL PROTECTED]>, > > [EMAIL PROTECTED] > > Resent-From: Jamie Heilman <[EMAIL PROTECTED]> > > Resent-To: [EMAIL PROTECTED] > > Resent-Cc: Craig Small <[EMAIL PROTECTED]> > > Resent-Date: Tue, 11 Dec 2001 02:48:03 GMT > > Resent-Message-ID: <[EMAIL PROTECTED]> > > X-Debian-PR-Message: report 123348 > > X-Debian-PR-Package: lprng > > X-Debian-PR-Keywords: > > From: Jamie Heilman <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Resent-Sender: Debian BTS <[EMAIL PROTECTED]> > > X-Sorted: Debian > > > > Package: lprng > > Version: 3.8.1-1 > > > > Package: ifhp > > Version: 3.4.4-1 > > > > Somewhere around lprng 3.8.0 something when horribly awry between the > > communication of ifhp and lprng. I've been using the following > > printcap for two printers for months without any problems, and now > > they both exhibit very odd behavior. > > > > clj4500|HP Color LaserJet 4500 > > :lp=clj4500%9100 > > :sd=/var/spool/lpd/clj4500 > > :filter=/usr/lib/filters/ifhp > > :sh:ifhp=model=hp4500 > > > > hplj6p|HP LaserJet 6P > > :lp=/dev/lp0 > > :sd=/var/spool/lpd/hp6p > > :filter=/usr/lib/filters/ifhp > > :sh:ifhp=model=hp6p > > > > The 6P doesn't have a postscript simm so I had to modify the ifhp.conf > > to include ghostscript converters for everything but raw pcl, those > > seem to still work fine though, its just the final sending of the data > > to the printer that bombs out. So here's where it gets odd, on the 6P > > I couldn't print anything, all I ever got from the printer was a > > response of, > > Filter_status: getting sync using 'pjl echo' at 18:07:48.544 > > Filter_status: no sync response from printer at 18:07:48.544 > > It would try 3 times and finally remove the job after 3 failures. So > > I added sync@ to my description, then it complained of no pagecount, > > so I added pagecount@ (keep in mind this all worked swimingly until > > recently without any of the mods) - at this point it started > > complaining about not being able to read the device. I rolled lprng > > back to the last 3.7 version but it didn't help either which made me > > suspect hardware failure. I got fed up and moved the printer to a > > different box. At the time I figured it was a parallel port issue. > > But then Color LaserJet 4500 started acting weird too and now I'm > > really puzzled. The clj4500 still prints PostScript files great - but > > now it if its sent plaintext it starts handing me the 'no sync > > response from printer' bit. This box is using its ethernet port and > > has always been pretty robust. My only thought is that something > > changed between the interaction of filters, specifically ifhp, and > > lprng recently and its caused a corruption of some kind that maybe > > persists between queued jobs (the only way I can explain lprng 3.7 not > > fixing the issue). Anyway, there's a newer version of ifhp out, it > > might fix the problems, it might not, but I thought I'd throw this out > > there. > > > > -- > > Jamie Heilman http://audible.transient.net/~jamie/ > > "...thats the metaphorical equivalent of flopping your wedding tackle > > into a lion's mouth and flicking his lovespuds with a wet towel, pure > > insanity..." -Rimmer > > > > ----- End forwarded message ----- > > > > > > ----- Begin forwarded message ----- > > > > ----------------------------------------------------------------------------- > 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. -----------------------------------------------------------------------------
