l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Jul 12 21:04

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] printer question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] printer question

also, this gets printed to my logfile when i try to print something:

   satan lpd[12188]: lp: job could not be printed (cfA003satan)

i wish lpd wouldn't print such verbose error messages...


begin Peter Jay Salzman <p@dirac.org> 
> i'm trying to configure an epson stylus color 600.
> when i print, the job simply disappears into the void without a trace.
> i know it gets spooled because if i stop lpd and try to print, the job
> appears in /var/spool/lpd/es600.  then if i enable lpd, the job
> disappears.  the printer lights never blink.  so SOMETHING right is
> happening.  at least as far as spooling the job goes.
> also, i can cat a file to /dev/lp0, so THAT'S working.
> forget that i haven't been able to get it working yet.  i have a
> different question.  i'd like to know where the job goes.
> here's the printcap i'm using:
> lp|lp720|Epson Stylus Color 600 - 720dpi:\
>    :lp=/dev/lp0:\
>    :af=/var/log/lp-acct:\
>    :lf=/var/log/lp-errs:\
>    :sd=/var/spool/lpd/es600:\
>    :sh:\
>    :pw#80:\
>    :pl#66:\
>    :px#1440:\
>    :mx#0:\
>    :if=/usr/local/sbin/es600-720:
> and here's /usr/local/sbin/es600-720
>    #!/bin/bash
>    #
>    # 720 dpi filter for the Epson Stylus Color 600
>    gs -q @stc600p.upp -sOutputFile=- -
>    echo "hello" >> /tmp/printer
> do you see where i'm about to go with this?  /tmp/printer never shows
> up.  i've set the input filter in printcap, but as far as i can tell,
> it's not being used.
> i hate setting up printers; maybe because i know so little about how
> printing works.   here's what i think happens:
> 1. lpr spools the job into the spool directory specified by printcap's sd.
> 2. lpd "somehow" knows the job is there and sends the job through the
>       input filter.
> 3. the input filter writes the translated job to standard out, which is
>       connected back to lpd.
> 4. lpd ships the job to the device, printcap's lp.
> Q1: is this correct?
> Q2: why am i not seeing "hello" in /tmp/printer?
> Q3: is there _really_ no debugging/verbose switches for lpd?
> note, installing lprng isn't an option.  the system that i'm using
> normally uses my laserjet 6MP, and i'd like to disturbe the printing
> system "as little as possible" so i don't muck up my laserjet
> configuration.
> plus, lprng comes with _way_ too much documentation.
> thanks,
> pete

GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E  70A9 A3B9 1945 67EA 951D
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.