| Michael Loßin on Wed, 6 Mar 2002 10:43:53 +0100 (CET)(envelope-from owner-apsfilter-help@apsfilter.org) |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| Re: No config files created by SETUP |
On 05-Mar-02 Stephan Windmüller wrote:
> So I installed the printer correctly, printcap looks like:
>
>| lp|cdj970;r=300x300;q=medium;c=full;p=a4;m=auto:\
>| :lp=/dev/lp0:\
>| :if=/etc/apsfilter/basedir/bin/apsfilter:\
>| :sd=/var/spool/lpd/lp:\
>| :lf=/var/spool/lpd/lp/log:\
>| :af=/var/spool/lpd/lp/acct:\
>| :mx#0:\
>| :sh
Looks good.
> But printing a test page out of opera still does not work.
Do other applications show the same results?
> Errors in /var/spool/lpd/lp/log show:
>
>| /bin/bash: /home/windy/.bashrc: Permission denied
This is weird... The .bashrc should only be parsed if the
shell is interactive (-> man bash), but here we use the
shell only for a script. We don't actually need the
contents of .bashrc, but that error shouldn't happen
anyway.
>| apsfilter warning: unknown option 'aiur'
If this is your host name, you are probably using some kind
of lpd that uses the host name as a class specification
(it's probably *not* LPRng). Nothing to be worried about
right now.
>| GNU Ghostscript 6.51: Unrecoverable error, exit code 1
Maybe it helps if you update ghostscript. Unfortunately
we don't get the exact error description here, but that
behaviour may have been fixed in the meantime.
>| sed: couldn't write 76 items to {standard output}: Broken pipe
We had that error reported a couple of times, and
I think it's caused by "psset" (which is a script).
Since psset is used in a pipe with ghostscript, it's
merely failing since gs exited, leaving the "read"
end of the pipe orphaned, thus breaking the pipe.
HTH
Michael