Date: Thu, 23 Oct 2008 22:22:57 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Martin Alejandro Paredes Sanchez <mapsware@prodigy.net.mx> Cc: freebsd-questions@freebsd.org Subject: Re: Printing to a Lanier LD160c does not work Message-ID: <20081024052257.GA5231@icarus.home.lan> In-Reply-To: <200810232142.41941.mapsware@prodigy.net.mx> References: <101620082036.391.48F7A5DA0009DFCD0000018722120207849C05020E089F060E@comcast.net> <20081016212000.GA3960@icarus.home.lan> <200810232142.41941.mapsware@prodigy.net.mx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 23, 2008 at 09:42:41PM -0700, Martin Alejandro Paredes Sanchez wrote: > El Jue 16 Oct 2008, Jeremy Chadwick escribió: > > On Thu, Oct 16, 2008 at 08:36:42PM +0000, ajphanks@comcast.net wrote: > > > I am trying to setup a Lanier LD160c (admincolor) that has a network > > > interface. I am new to FreeBSD and tried to follow the handbook. I am > > > able to print to a HP 5SI (corp-admin) with no problems. There are no > > > errors in the lpd-errs and the file is drained from the queue, but the > > > printer does not print anything. And this is a working printer to > > > Windows. lpr -P admincolor testfile.txt > > > > > > printcap: > > > corp-admin|hp|laserjet|Hewlett Packard LaserJet 5Si:\ > > > > > > :lp=\ > > > :sd=/var/spool/output/corp-admin:rm=corp-admin:\ > > > :lf=/var/log/lpd-errs:\ > > > :if=/usr/local/libexec/crlfilter:sh:tr=\f:mx#0: > > > > > > admincolor|hp|laserjet|LANIER LD160c RPCS:\ > > > > > > :lp=\ > > > :sd=/var/spool/output/admincolor:rm=admincolor:\ > > > :lf=/var/log/lpd-errs: > > > > If this printer is hooked up on the network (e.g. via Ethernet), I > > believe you need to set the lp variable to the hostname or IP address of > > the printer, e.g.: > > > > admincolor|hp|laserjet|LANIER LD160c RPCS:\ > > > > :lp=192.168.1.100\ > > :sd=/var/spool/output/admincolor:rm=admincolor:\ > > :lf=/var/log/lpd-errs: > > > > Negative, leave the lp capability blank, explicitly (:lp=:). > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing-advanced.html#PRINTING-ADVANCED-NETWORK-RM Then the printcap(5) man page should reflect this; the existing explanations for both fields are painfully terse. lp str /dev/lp device name to open for output, or port@machine to open a TCP socket rm str NULL machine name for remote printer I can file a PR (to doc) on this if recommended. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081024052257.GA5231>