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

Bug#923532: closed by Brian Potkin <claremont102@gmail.com> (Re: Bug#923532: cups-bsd: spool directory fills up)



Hello Brian,
On Mon, Mar 04, 2019 at 03:45:05PM +0000, Debian Bug Tracking System wrote:
> On Mon 04 Mar 2019 at 11:37:46 +0100, Helge Kreutzmann wrote:
> 
> > On Sun, Mar 03, 2019 at 01:54:56PM +0000, Brian Potkin wrote:
> > 
> > > I'd suggest you put "PreserveJobFiles 30" (and other smallish values)
> > > in cupsd.conf, then print and see whether you can have confidence in
> > > the option being functional. My tests indicate it is reliable. In which
> > > case you should not experience the spool directory getting clogged up
> > > in future.
> > 
> > I will test this, but then at least the documention is wrong, because
> > cupsd.conf(5) says:
> > 
> > PreserveJobFiles seconds
> > … The default is "86400" (preserve 1 day).
> > 
> > So I set the value to 30, printed one file which does not print and
> > nothing vanish, even after several minutes. 
> > 
> > I then cancel the job with "cancel" (not my usual lprm). This works.
> > But again, the file d* is not deleted after the 30 seconds are over.
> 
> It won't be. PreserveJobFiles handles files which have gone through the
> filtering system. There could many reasons a file is not printed; a
> user would not want it to be removed while the error is rectified.
>  
> > So to conclude cups is missing a mechanism to remove uprintable files
> > in the spool directory. 
> 
> I don't experience this. 'cancel -ax' serves to remove a user's c and d
> files.

Unless there is an error, then it does not. This is the use case I run
into (thought previously I used lprm)

> > So the best way is probably a good old "rm d00*" in a suitable cron
> > job, e.g. cron.weekly.
> > 
> > Thanks for your help.
> > 
> > If any of this knowledge is worth putting into a bug report somewhere
> > I can do that of course.
> 
> PreserveJobFiles with "yes" or "no" or a seconds value and 'cancel -ax'
> appear to work as intended for managing /var/spool/cups. I will close
> this report.

I agree that it works as intended. It is just that a mechanism for
removing failed jobs is in my opinion missing. As you stated such a
mechanism is not intended, so I installed a simply cron job for this.

Greetings

       Helge


-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: Digital signature


Reply to: