printer difficulties

[Derek Martin]

On Fri, 10 Dec 1999 dmoylan at ibm.net wrote:

> 
> 
> have been messing about installing a new printer under rh5.2 on toshiba
> laptop, and have encountered (to me) inexplicable error manifestations.
> 
> after encountering difficulties, i removed /var/spool/lpd files as well
> as /etc/printcap and started from scratch using the control-panel printtool.  
> the difficulties persist.
> 
> the stuff in /var/spool/lpd looks normal (to me)
> 
> ##################################################################
> /etc/printcap  looks like this:
> # This file can be edited with the printtool in the control-panel.
> 
> ##PRINTTOOL3## LOCAL POSTSCRIPT 300x300 letter {} PostScript Default {}
> LW-LOC:\
> 	:sd=/var/spool/lpd/lw-loc:\
> 	:mx#0:\
> 	:sh:\
> 	:lp=/dev/lw-loc:\
> 	:if=/var/spool/lpd/lw-loc/filter:
> 
> ##################################################################
> /usr/sbin/lpd:
> exists
> /dev/lw-loc points to /dev/ttyS0
> both have full permissions
> 
> ##################################################################
> % cat /usr/tmp/0log.PS > /dev/lw-loc
> prints the file ok
> 
> ##################################################################
> % lpr -PLW-LOC /usr/tmp/0log.PS  gives:
> lpr: connect: No such file or directoryt
> jobs queued, but cannot start daemon
> 
> ##################################################################
> % lpc status   gives:
> LW-LOC:
> 	queuing is enabled
> 	printing is enabled
> 	1 entries in spool area
> 	no daemon present
> 
> ##################################################################
> % lpc up LW-LOC   gives:
> LW-LOC:
> 	printing enabled
> lpc: connect: No such file or directory
> 	couldn't start daemon
> 
> ##################################################################
> % lpq -PLW-LOC gives
> Warning: no daemon present
> Rank   Owner      Job  Files                                 Total Size
> 1st    moylan     4    /usr/tmp/0log.PS                      8537 bytes
> 
> ##################################################################
> 
> i might add that everything  worked formerly, but changes do get made
> here and there and i must have destroyed something necessary.  but what?
> it's gotta be basic.

I'm just taking a stab here, but I seem to recall having run into cases
where some older programs don't like symlinks.  Try changing the device
to ttyS0 and see if it works.

-- 
Derek D. Martin
Senior UNIX Systems/Network Administrator
Arris Interactive
derek.martin at ne.arris-i.com

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).