Startup and shutdown
Run one instance of P4Thumb for each server in which you want to enable thumbnails. Do not run multiple instances of P4Thumb using the same client view and server. (You might improve performance by running multiple instances with differing client views, for example one instance for each large project.)
The user associated with P4Thumb:
- Does not need to be dedicated to P4Thumb, but the workspace must be dedicated for use only by P4Thumb.
- Must have admin privileges on the server to run the daemon.
The first time you start P4Thumb for a specified Helix server, it creates thumbnails for all images in its client view, which is likely to affect server performance. After the initial thumbnails are created, P4Thumb does not have a significant effect on server performance.
To start P4Thumb:
Issue the following command specifying the server containing the images files, the workspace for P4Thumb to use, and the Helix Core username associated with P4Thumb activity:
p4thumb -c <config files> [options]
The following table describes the available switches.
Switch | Description |
---|---|
-v |
Writes verbose status output to console. Default value is silent. |
-d |
Deletes thumbnails from server. Must use with -n (a ChangeListRange in the configuration file). |
-f |
Forces to always write thumbnail. Default skips if set. |
-V |
Prints application version and exits. |
-test <testFile> |
Tests thumbnail conversion of testFile and exits. |
To stop P4Thumb:
In the command window used to start P4Thumb, type CTRL-C.
By default, when you restart P4Thumb, it resumes processing starting with the last changelist that was processed. P4Thumb maintains a counter for this purpose on the specified server. Starting P4Thumb from a specified changelist using the -n flag resets this counter if it exceeds the specified value. Deleting thumbnails does not affect the counter.
Your search for returned result(s).