Re: lprm vs. apsfilter

[Michael Loßin <phallobst@xxxxxx>]

Steffen Hein wrote:
> 
> Hallo friends,
> 
> running apsfilter since FreeBSD 2.2.8, I noticed  an
> unpleasant behavior after the lprm command since
> upgrades 4.0-4.3  ( in the default  installation. You
> - better than me - identify the pertinent apsfilter
> versions.)
> 
> Formerly, the lprm statement  recursively removed all
> printing orders from the spooler and stopped the printer.
> Since then, the last order seems to be removed , but my
> printer (HP-Deskjet 850C) continues spitting out 'garbadges'.

Maybe there's a 'gs' process running wild... Normally it
should've been stopped with lprm. Which spooler are you
using? Maybe it uses some signal other than SIGINT to stop
apsfilter.

> There seems to be no conventional means to stop lp.
> Page after page, two lines of  hieroglyphs, then the next page...
> Further 'lprm' commands, even repeated from root (or off-
> switching the printer,  clearing its memory, etc. ) have
> no effect. - The spook only disappears after reboot.

Check for ghostscript processes still running and kill them.
Switching off the printer only blocks the gs process until
the printer is ready to take data again.

> A genuine UNIX command, such as lprm, should  remain
> effective under any application - shouldn't it ?

I haven't experienced problems for the last couple of months.


Michael