Michael Loßin on Thu, 28 Feb 2002 12:11:46 +0100 (CET)(envelope-from owner-apsfilter-help@apsfilter.org)


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: Again - it doesnt print for some reason


On 28-Feb-02 Andrei Loukinykh wrote:
> 
>  There's really something with permissions in printing system, I think:
> 
> IF filter 'apsfilter' filter msg - 
> '/usr/local/etc/apsfilter/basedir/bin/apsfilter: line -221:  2786
> Segmentation fault      gs -q -dNOPAUSE -dSAFER -dPARANOIDSAFER
> -sDEVICE='ljet4' -sPAPERSIZE='a4' -r'600x600' -sOutputFile=- -' at
> 2002-02-28-08:36:05.666 ## A=root@cow+760 number=760 process=2762
> IF filter 'apsfilter' filter msg - 'sed: couldn't write 36 items to
> {standard output}: Broken pipe' at 2002-02-28-08:36:05.699 ##
> A=root@cow+760 number=760 process=2762
> IF filter 'apsfilter' filter msg - 'cat: write error: Broken pipe' at
> 2002-02-28-08:36:05.699 ## A=root@cow+760 number=760 process=2762

I don't know if it really is a permission issue, but something
is *seriously* wrong on your system.

Most prominently, it's the "sed" error that's bugging me.
In apsfilter-7.2.2, there's only one occasion of sed usage:

<--- snip --->
DRIVER_SCRIPT="$PRINTER"
if [ ! -e "$CONF_DIR/basedir/driver/$DRIVER_SCRIPT" ]; then
  # get the script name from the mapping file
  DRIVER_SCRIPT=$(grep ":$PRINTER:" \
    "$CONF_DIR/basedir/driver/MAPPING" | sed "s/:.*//")
fi
<--- snap --->

But in your case (PRINTER is "ljet4"), apsfilter isn't even
supposed to enter the "if" block, since the driver script
for ljet4 does exist.

One cause for this problem might be the "basedir" link
in /usr/local/etc/apsfilter -- please check if it *really*
points to the correct destination directory (which is
probably /usr/local/share/apsfilter).

Maybe something went wrong during installation; you might
want to try to remove the whole apsfilter package and
re-install (and probably rebuild printcap).


The other "broken pipe" error messages are just a consequence
of one program failing, bringing down the whole pipe
contruct (of which there are quite a number in apsfilter).

>  Possibly, I need to change /etc/lpd.conf or /etc/lpd.perm
> Is there anyone here to share one with me, where it works with apsfilter ?

Under LPRng you can try "checkpc -f" -- this tool corrects
any permission problems. I haven't changed any permission
defaults for my LPRng installation -- no problems here.


HTH
Michael