Thank you for your report, Emin.
On Fri 08 Feb 2019 at 19:33:59 +0100, Emin Kaya wrote: > Package: cups > Version: 2.2.10-3 > Severity: normal > > Dear Maintainer, > > We need to clear up the Job History each day, to have a clear History > for the next day to account print jobs a customer prints to one of our > preconfigured printers. > > To do this, we found "JobPreserveHistory <seconds>" as root option in > the documentation for /etc/cups/cupsd.conf, which would do the job > perfectly. PreserveJobHistory? > We set the option with a one day timeframe value of 86400 seconds via > the Webinterface for the configuration file (and later via nano...) > For our surprise, after restarting the service, All existing entries > were gone and as instead showing only the past print job entries I can reproduce that; the c and d files have been deleted. > within the last 86400 seconds, the /var/log/cups/error.log contain the > Error message > "E:[Timpestamp] cups sheduler stops through a program error" I cannot reproduce this. Do you still experience it? > After changing to the two other possible values "Yes" and "No" and > restarting the service cups went back to normal behaviour. > > It seems, that despite the documented proposed behaviour, cups > sheduler cant handle the numeric value for a one day timeframe. > > We didn't tried out lower values, as expecting that this value work > for other option as expected. > > I hope, this error can be fixed fast. >From my tests it seems that PreserveJobHistory cannot handle being given any seconds value, small or large. What do you get with 30 for PreserveJobHistory? Regards, Brian.
