« Back to User Guide
You can find your version of java by running
java -version java version "1.6.0_06" Java(TM) SE Runtime Environment (build 1.6.0_06-b02) Java HotSpot(TM) Server VM (build 10.0-b22, mixed mode)
Download and unzip ProductClient.zip from the releases page. This includes shell scripts for unix and a batch file for windows.https://github.com/usgs/pdl/releases
You can upgrade to the latest version by replacing ProductClient.jar and restarting the process.
For Linux users, the PDL client can be started automatically on client machine reboot. This requires adding PDL's init.sh shell script to be added to the Crontab table. Calling the init script from the crontab will automatically start, or restart if the process isn't running, the PDL client application.
To add an entry to the crontab table, execute:
sudo [pdluser] crontab -e
...where [pdluser] is the client machine's user ID for running PDL.
After asking for your password, this will bring up the crontab table using your system's default editor (you must be listed in your system's sudoers table to perform this operation. See this link for adding a user to sudoers) Add the following to crontab, where PDL_CLIENT_DIR is the location of the ProductClient PDL Client directory:
# start (if not already running) every five minutes */5 * * * * PDL_CLIENT_DIR/init.sh start >/dev/null 2>&1 &
In the above crontab snippet, the five asterisks specify the runtime minute, hour, day-of-month, month and day-of-week. Under Linux systems, "*/5" will evaluate to "run every 5 minutes." This should also work on BSD Unix systems such as Mac OS X. An alternative syntax explicitly names the minutes after the hour in a comma-separated list:
# start (if not already running) at 5, 10, 15, ...minutes after the hour 5,10,15,20,25,30,35,40,45,50,55 * * * * PDL_CLIENT_DIR/init.sh start >/dev/null 2>&1 &
The redirect to
dev/null throws away standard output and
2>&1 redirects standard error output to the same stream as
standard output (throw away). The ending ampersand launches init.sh in the
NOTE: the init script assumes
java is on the
system PATH. You may need to configure a crontab path, or update the init
script to use an absolute path for