2018.1

complete before pausing. Once paused, the service is still "started" but will wait until it is
activated again before processing jobs. This is very useful if you want to receive jobs from
external services (such as with the LPD Server) but not process them right away.
To kill (force quit) a service:
1. Right-click on the running service.
2.
Click on Kill.
3.
Click OK to confirm on the warning.
If the service is currently processing a file, execution will stop and the action will not
complete. If the action was partially completed (for example writing a large file), the partial
action is not undone. As this may lead to corrupted or incomplete files, it is strongly
advised not to kill a service unless it is absolutely necessary to do so.
Viewing log files
The second major role of the Service Console is to view and browse log files. The Service
Console can both view existing log files, or monitor the log file for the current day and update
the view in real time.
When a service is selected on the left pane, its log file (if any exists for the current day) is
displayed. The log displays in a tree fashion. The log itself is the root, and each session (the
time between the start and stop of a service) is listed. Under each session, each time a process
runs, a new branch is created and it can be expanded to see each action within that process.
Log viewer settings
The log viewer for the current day is normally live, meaning it updates automatically as the log
file is updated by the appropriate service. There are a few options to change this behavior,
which could be useful when a service is under heavy load.
These options are found in the View menu:
l
Update speed: Refreshes the view based on a timer.
l
Pause monitoring: Pauses or resumes the update.
To refresh the log viewer, press F5 or select File > Reload.
Page 625