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

Bug#923532: cups-bsd: spool directory fills up



Hello Brian,
On Sat, Mar 02, 2019 at 01:14:29PM +0000, Brian Potkin wrote:
> Thank you for your report, Helge.

Thanks for the quick reply.

> On Fri 01 Mar 2019 at 15:30:48 +0100, Helge Kreutzmann wrote:
> > By chance I noted that the spool directory fills up over time,
> > currently:
> > root@samd:/var/spool/cups# lpq -a
> > Keine Einträge
> > root@samd:/var/spool/cups# du -hs .
> > 166M    .
> > root@samd:/var/spool/cups# ls -lh | wc -l
> > 621
> > 
> > The oldest files are from 2017. There are two types of file, some
> > short text files which seem to describe the print job and pdf and
> > postscript files, which appear to be the print jobs themselves.
> 
> c (control or history) files and d (document) files. They should get
> cleared with 'cancel -a -x' but might need to be removed with 'rm'.

Thanks for the pointer. I usually use "lprm" and always thought that
removing a job also removes all spool files. I did not know about the
command cancel, whose name does not lead to beeing printing specific
(neither starts with cups nor with lp).

Do you think implying "-x" with with lprm would be a worthwile
wishlist bug for upstream?

> > Some files / queues on my system do not print 
> > so I have to abort the jobs with lprm. If these files are really
> > (only) this use case I don't know.
> > 
> > If I should run some tests (I currently have an unprintable file at
> > hand) please tell me.
> > 
> > As a band aid a cron job could be added which deletes files there
> > older let's say than a week.
> 
> cupsd.conf(5) explains the PreserveJobFiles and PreserveJobHistory
> directives. If you put "PreserveJobFiles 30" in cupsd.conf, does it
> work for you?

Neither are currently explicitly set. But the man page says that
PreserveJobFiles has a default value of 1 day and PreserveJobHistory
is yes. Maybe PreserveJobFiles only applies to sucessfully printed
jobs?

> You may, of course, alter the default PreserveJobHistory value too
> but are then likely to hit Bug#921741. Knowing how much of Emin Kaya's
> issue you can replicate would be useful.

Just to be clear: I should first try out PreserveJobHistory? And after
a day all spool files should be gone (if it works)?

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: