On 19-Apr-2017, Brian Potkin wrote: > On Thu 20 Apr 2017 at 06:32:08 +1000, Ben Finney wrote: > > How can you tell that a job doesn't get that far? > > It would have printed. You record that it didn't. Oh, I thought you were seeing something in the output that independently verified that, so I wanted to know what that information was :-) > > > Set up this print queue (as root): > > > > > > lpadmin -p testq -v /home/<user>/testq-out -E -P </etc/cups/ppd/<PPD_for_the_Samsung> > > […] change it to "-v file:/home/<user>/testq-out". The idea is to > discover whether the job goes through the filtering system. ===== $ sudo lpadmin -p testq -v file:/home/bignose/testq-out -E -P /etc/cups/ppd/SCX-4623-Series.ppd lpadmin: File device URIs have been disabled. To enable, see the FileDevice directive in "/etc/cups/cups-files.conf". $ sudo emacs /etc/cups/cups-files.conf $ grep FileDevice /etc/cups/cups-files.conf FileDevice Yes $ sudo lpadmin -p testq -v file:/home/bignose/testq-out -E -P /etc/cups/ppd/SCX-4623-Series.ppd lpadmin: File device URIs have been disabled. To enable, see the FileDevice directive in "/etc/cups/cups-files.conf". ===== -- \ “Following fashion and the status quo is easy. Thinking about | `\ your users' lives and creating something practical is much | _o__) harder.” —Ryan Singer, 2008-07-09 | Ben Finney <bignose@debian.org>
Attachment:
signature.asc
Description: PGP signature