Ulpt problems.

Warren Block wblock at wonkity.com
Mon Jul 27 00:20:36 UTC 2015


On Mon, 27 Jul 2015, Bernt Hansson wrote:

>       The filters can be tested directly.  Send some text to the filter:
>
>         lptest | /usr/local/libexec/enscript
>
>       It will produce a bunch of PostScript output, the last lines of which are:
>
>         %%Trailer
>         %%Pages: 4
>         %%DocumentNeededResources: font Courier-Bold Courier
>         %%EOF
>         [ 4 pages * 1 copy ] left in -
>
>       If that does not work, check the contents of the /usr/local/libexec/enscript file and the permissions set on it.
> 
> 
> The content of enscript is;
> 
> #!/bin/sh
> /usr/local/bin/enscript -o -

Wait, so it did not work?  What happened?  What does
   ls -lh /usr/local/bin/enscript
show?

> /etc/printcap
> 
> lp:\
>         :lp=/dev/ulpt0:\
>         :sh:\
>         :mx#0:\
>         :sd=/var/spool/lpd/lp:\
>         :lf=/var/log/lpd-errs:

That is not the printcap shown in the examples.  Note the missing "n" in 
"unlpt0".  That is important for some printers.  But this printcap does 
not have a filter, either, so it is not related to the problem above. 
Let's fix one thing at a time.


More information about the freebsd-questions mailing list