![](https://seccdn.libravatar.org/avatar/e74e753692df94fa04f5826ba79f6d8c.jpg?s=120&d=mm&r=g)
Hello, I attempted to setup the cups-server running on our printer-server (SUSE Linux 10.0) to 1. save/store the jobs users sent there, 2. keep always only 200Mb of such data with 3. deleting automatically the oldest ones. (So in fact having a well-defined quota-system, managed automagically.) Is there please an easy setup to achieve that? Thank you in advance, Pelibali
![](https://seccdn.libravatar.org/avatar/ec01af9ac65ddc7945720a7b71902886.jpg?s=120&d=mm&r=g)
pelibali wrote:
Hello, I attempted to setup the cups-server running on our printer-server (SUSE Linux 10.0) to 1. save/store the jobs users sent there, 2. keep always only 200Mb of such data with 3. deleting automatically the oldest ones. (So in fact having a well-defined quota-system, managed automagically.) Is there please an easy setup to achieve that?
Dear Pelibali, for question 1) set PreserveJobFiles Yes in cupsd.conf Questions 2 and 3 might be solved with a simple cronjob (in directory /var/spool/cups). Best Joachim
![](https://seccdn.libravatar.org/avatar/ba6138f793e72be6644854fdc3ec2f02.jpg?s=120&d=mm&r=g)
Hello, On Jan 23 22:49 Joachim Kieferle wrote (shortened):
pelibali wrote:
Hello, I attempted to setup the cups-server running on our printer-server (SUSE Linux 10.0) to 1. save/store the jobs users sent there,
/etc/cups/cupsd.conf: PreserveJobFiles See the "CUPS Software Administrators Manual".
2. keep always only 200Mb of such data with
No. How should this work when a user submits a print-job which is 201 MB?
3. deleting automatically the oldest ones.
/etc/cups/cupsd.conf: MaxJobs See the "CUPS Software Administrators Manual".
(So in fact having a well-defined quota-system, managed automagically.)
What do you mean with quota-system? For printer specific quotas for each user see "man lpadmin" (job-quota-period must be set in any case to have quota support) This quota support is fairly primitive - a single quota applies to all users for a single queue. The information is tracked on-the-fly by the cupsd from the job history information. Several third party applications exist which work with CUPS to do quota management e.g. the free software PyKota or PrintBill.
Questions 2 and 3 might be solved with a simple cronjob (in directory /var/spool/cups).
But only when cupsd does not run at the same time. Changing cupsd's "own" files while it is running is a perfect method to get it so confused that it will no longer work and/or no longer start again, see for example http://lists.suse.com/archive/suse-linux-e/2004-Jun/4134.html and for a related issue see: http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html -------------------------------------------------------------------------- The configuration files are not reloaded for every print job. Rather, cupsd keeps much of the information in the main memory and writes information back to the configuration files whenever needed. ... Never copy configuration files from other systems to your system unless you know exactly what you are doing. Use command-line tools instead. -------------------------------------------------------------------------- Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
participants (3)
-
Joachim Kieferle
-
Johannes Meixner
-
pelibali