Problems with printing

Warren Block wblock at wonkity.com
Thu Apr 22 19:28:54 UTC 2010


On Thu, 22 Apr 2010, Frank Wi?mann wrote:

> Warren Block schrieb:
>> On Thu, 22 Apr 2010, Frank Wi?mann wrote:
>> 
>>> I'm facing serious problems with my new bought HP ColorLaserjet 2025dn.
>>> I plugged it in the right interface and it got detected. I did set up 
>>> /etc/printcap as following:
>>> 
>>> p|local line printer|HPColorLaserjet:\
>>>        :lp=/dev/ulpt0:\
>>>        :sh:\
>>>        :mx#0:\
>>>        :sd=/var/spool/lpd/HPColorLaserjet:\
>>> #       :if=/usr/local/libexec/ps2pcl:\
>>>        :if=/usr/local/libexec/psif:\
>>>        :lf=/var/log/lpd-errs:
>> 
>> That whole printer definition is one long line; backslashes are line 
>> continuation characters.
>> 
>> Because of that, you can't just comment out individual sections. Remove the 
>> whole ps2pcl filter line.
>> 
>> That may not be the whole problem, but it's a start.
>
> Removing the line and restarting lpd/retrying printing didn't do anything. No 
> mails, no error messages, no printing.

There's a missing "l" at the start of that entry, maybe just a cut and 
paste error.

See what chkprintcap(9) says.  Also 'lpc status lp'.

> By cd'ing into /var/spool/lpd to look after queued jobs I noticed that the 
> whole file structure under that directory belongs to "root:frank" whereas the 
> /var/spool/lpd/-directory is owned by "root:daemon". Does that matter?

Don't know, but I set group and owner to daemon:daemon.  Incidentally, 
using the first name of the printer (lp) for the spooldir would make 
more sense to me.

-Warren Block * Rapid City, South Dakota USA


More information about the freebsd-questions mailing list