Problem:

We are receiving the following error message when attempting to start the License Manager and we don't understand Pipe Create Error:

Starting MFLM License Manager

MF-LMF:Thu Aug 14 08:58:35 2008: LMF Starting

MF-LMF:Thu Aug 14 08:58:35 2008: Pipe Create Error

MF-LMF:Thu Aug 14 08:58:35 2008: ENOENT(2): No such file or directory

MF-LMF:Thu Aug 14 08:58:35 2008: LMF Closing Down

Resolution:

License Manager uses named pipes as temporary files and creates them in the location defined by the UNIX operating system setting of P_tmpdir. This is typically /tmp. You might want to relocate the named pipes. When License Manager is launched it creates one long-lived named pipe, called LMF-common, which exists until License Manager is closed down. While it is running, it also creates a number of transient named pipes that exist only for a short time.

You might want to relocate LMF-common to a different directory so that you can delete all entries in the temporary directory without having to explicitly exclude this pipe. To do this, you must include in the job that starts License Manager the environment variable LMFCOMM. This environment variable must be set before your job executes the command to start License Manager. The format of LMFCOMM is:

LMFCOMM=directory

Where directory is the full path name of the directory that is to be used by License Manager to place its named pipe LMF-common. For example:

LMFCOMM=/usr/templmf

export LMFCOMM

The directory specified by LMFCOMM must have full read/write/execute permission for all users who will be using the licensed development system. In addition, all development system users must also set LMFCOMM in their own environment to the same value as that used by License Manager. If this is not done, then users will be unable to contact License Manager and obtain a license unit.

The "Pipe Create Error" occurs when the environment variable has been set but the directoryreferenced does not exist. Either unset the variable or create the required directory.