KB Home | Change the Nightly Maintenance schedule times
You can change the time that PaperCut will perform it’s nightly maintenance by using the Config Editor. By default these run at 12:55am (the Config Key setting is schedule.daily-maintenence=0 55 0 * * ?).
Prior to version 11.2 the daily maintenance tasks were run at 1:15am. This was changed to avoid issues around daylight savings change overs, which could result in the job not being run.
A number of different scheduled tasks run during the nightly maintenance, principally a synchronisation to add new PaperCut users and groups against your defined synchronisation source.
The format of the value is a string comprised of 6 fields separated by white space. The format is similar to the “cron” format which is a job scheduler used in Linux & Unix. Fields can contain any of the allowed values, along with various combinations of the allowed special characters for that field. The fields are as follows:
Field Name Mandatory Allowed Values
- YES 0
Minutes YES 0–59
Hours YES 0–23
Day of month YES 1–31 ? or *
Month YES 1–12 or JAN-DEC or ? or *
Day of week YES 1–7 or SUN-SAT or ?
The question mark (?) can be considered to be the same as saying “any”. For example; if I want my maintenance to run on a particular day of the month (say, the 28th), but I don’t care what day of the week that happens to be, I would put “28” in the day-of-month field, and “?” in the day-of-week field.
The asterix (*) can be considered to be the same as saying “every”. For example; if I want my maintenance to run on a particular day of the month (say, the 28th), but I want it to run every month, I would put “28” in the day-of-month field, and “*” in the Month field.
From the example above we have:- 0 0 3 28 * ? Which means… Run at 3AM - on the 28th day of the month - every month - on any day of the week.
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.