On Apr 04 21:54:30, Girish Venkatachalam wrote: > On Wed, Apr 4, 2012 at 9:40 PM, Jan Stary <[email protected]> wrote: > >> Failed. It is silent. > > > > What failed? How does your /etc/printcap describe the printer? > > > > I just modified from the default remote printer commented out section. > > rm=<ip> > > lpr is from /usr/bin, not LPRng > > I tried that as well. > > lpq lists the jobs but nothing happens/moves in the printer. >
Repeat: how does your printcap decribe the printer? As in: show me your printcap. > Having used to protocols all my life I was curious why it would not greet me. > > That is all. So I wanted a way to see if it was alive. > > >> so LPD seems sane but it refuses to respond. > > > > What LPD, the printer's LPD daemon? > > How do you talk to it that you know it refuses to respond? > > > > Printer works. It prints from Mac machine, not from OpenBSD. So it is alive, and does not refuse to to respond, right? > > If it doesn't speak postscript, you might need to > > preprocces the printing jobs using the PPD file, > > using something like > > > > HP:\ > > :lp=:rm=a.dd.re.ss:rp=name:\ > > :af=/etc/foomatic/file.ppd:\ > > :if=/usr/local/bin/foomatic-rip:\ > > :sd=/var/spool/output:\ > > :lf=/var/log/lpd-errs:\ > > :sh: > > > > I will try that and reply. Hold on. > > I am wondering whether there is something else I can do. > > I am guessing your /etc/foomatic/file.ppd is nothing but > > $ gunzip > /usr/local/share/foomatic/db/source/PPD/HP/hp-laserjet_professional_m1213nf_mfp-hpijs.ppd.gz file.ppd is nothing but a made up name for a file that you need to replace with the right PPD file for that printer. > OpenBSD has never give me so much trouble before. ;) It is not OpenBSD that is giving you trouble.
