These settings determine how long unprinted jobs and job history data remain in the system. They also contain timeouts and other settings. If not set, the system defaults apply.
To keep your changes, click Save.
Parameter |
Explanation |
---|---|
How many hours Sentinel keeps a print job in its queue when a print request is made by a user but not released. After this period of time, the job is cleared but an entry is made in the log. Default: 12 hours. |
|
Clear history after [X] days |
How many days Sentinel keeps print jobs on the History screen. Default: 30 days. |
Clear log after [X] days |
How many days Sentinel keeps entries in the log. Default: 30 hours. |
AutoPrint TimeOut |
This is only relevant when AutoPrint is allowed on a device (usually a virtual device “0.0.0.0”), or if a user is allowed to print automatically (AutoPrint enabled for that user in Settings). Normally, when a user wants to print, the print job request is picked up by the Sentinel server and sent to the database. When the user is correctly identified at the device controller, the server retrieves the print job from the database and releases it. AutoPrint jobs, however, bypass the device controller. The server sends the print job request to the database and immediately tries to release it. If the Sentinel database is on the same computer as the Sentinel server, there is no problem. But if the database and server are on two computers that are far apart, the database may not have time to receive the information about the print job that the server is already trying to release. To avoid this problem, use this parameter to create a delay (for example, three seconds). This allows the database time to receive print job information before the server releases the job. Default: 2 seconds. |
SNMP TimeOut |
This is only relevant when SNMP Count is selected for a device. SNMP continually monitors printer status, completion of jobs, number of pages printed, etc. Since Sentinel adds an additional communication chain to the process (print request —> the Sentinel server —> the Sentinel database, then user recognition at device controller —> the Sentinel server —> the Sentinel database —> release job), there can be a delay between actual printing activity and what is in the Sentinel database. For example, a user sends a 100 page printout and the job is recorded in the Sentinel database. But the user decides to cancel the job physically at the printer after only three pages were printed. From Sentinel’s perspective, 100 pages were printed. To avoid this problem, use this parameter to create a delay (for example, two seconds) after the SNMP status request. This is the amount of time the server waits before checking the printer to see how many pages were actually printed. Default: 60 seconds. |
Disable printing on printer error |
If selected, the Sentinel server checks the status of the destination printer before releasing print jobs to it. If the printer status is Error, then the print jobs are not released. |
Show quota on panel |
If selected, after user identification, the user’s quota (and remaining pages) is shown on the device’s display. |
Show user description on panel |
If selected, after user identification, the user's description is displayed instead of the user name. |