PGP Command line uses specific versions of shared libraries that may differ from those required or used by other applications on the server.

You may get the following error when running PGP Commands:

PGPSDK is running in local mode.

In many cases, creating a wrapper script and placing it in the existing global path will allow PGP to run successfully without disrupting the functionality of other installed software.

Below is an example of one such script.  This will need to be adapted to the specific environment.

For example, some systems use LD_LIBRARY_PATH rather than LIBPATH. Typically the script itself will be called 'pgp' and it will have permissions set to 755 or 555.

#!/bin/sh
PGPDIR=/opt/pgp  
ulimit -n 2000
PATH=$PGPDIR/bin
LIBPATH=$PGPDIR/lib pgp "$@"    

Such a script can also be used to allow a group, such as a development group, to use PGP without having to license it for each individual user. In such a case you will want to create (or use) a directory that is readable and writeable by the desired group. It may also be necessary to create the group and add relevant users to the group. This line can be added to the wrapper script.

PGP_HOME_DIR=/path/to/group/read-writable-location/

This will cause PGP to store licensing and configuration information and keyrings in the /path/to/group/read-writable-location/ directory. If the group ownership is set to the relevant group and the group is given read, write and execute permissions on the directory and read and write permissions for any files, any member of the group will be able to use PGP without having to individually license the software.