Summary: | some better printing guidance? | ||
---|---|---|---|
Product: | [OLD] Docs-user | Reporter: | ivo welch <ivo.welch> |
Component: | Printing HOWTO | Assignee: | Docs Team <docs-team> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | printing |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://localhost:631/printers/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ivo welch
2004-10-24 14:18:19 UTC
What's in http://localhost:631/printers/laser?which_jobs=completed Replace laser with your printer name. Why lpr? What's wrong with lp? What does lpstat -t show? Check files in /var/log/cups/ Your spool is /var/spool/cups/ what's wrong with lpr? ;-) lp works. lpr does not. I guess I came the wrong unix route. I wonder if this is a bug in the system, or a weird config on my part. if it is neither, then perhaps the docs should say so. many thanks for the note. I was just totally baffled. the suggestion about adding the localhost interface should still be useful. /iaw I am not aware of issues when using lpr instead of lp with cups apart from the fact that the switches are different: lp -d printer / lpr -P printer "Adding the localhost interface": I suppose that you mean displaying the url instead of the ugly "here" link. I agree. Fixed link to "here". Sending bug back to docs-team in case anyone has any comment on the lp vs. lpr issue. printing-team: what's the difference between cups' lp and cups' lpr? Why would lp work and lpr not? 18:17 <@spyderous> lpr submits files for printing. 18:17 <@spyderous> lp submits files for printing or alters a pending job. Lovely thing is, the CUPS docs say: """ Both lp and lpr are supported ways of queuing your job for printing. However it suggested you use lp because it is what cups was designed around. """ Anyway, marking as FIXED (now that we know what lp/lpr differ in *cough* :) |