Ulpt problems.

Bernt Hansson bah at bananmonarki.se
Mon Jul 27 01:21:48 UTC 2015



On 2015-07-27 02:20, Warren Block wrote:
> 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?
>
-r-xr-xr-x  1 root  wheel   187K 10 Jul 11:07 /usr/local/bin/enscript
>> /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.
Well "n" or no "n" The printer is stone cold. I'll try a reboot to see 
if that loosen up things.


More information about the freebsd-questions mailing list