Managing the automounter for UNIX

Rational® Synergy can run with an automounted installation area and automounted databases.

The following are some issues to consider when using the automounter with Rational Synergy.

Automounted database paths

An automounted database path must be accessible using the same path on the GUI interface and engine machines.

Verify that a database path is accessible by changing directories to the official database path on the GUI interface and engine machines.

Paths passed to machines not running the automounter

When a pwd or getwd command is run on an automounted file system, often the /tmp_mnt prefix is added to the path. Among programs running on machines with the same file system automounted, the paths are recognized. However, if that same path is passed to a program on a machine on which the file system is not automounted, the program cannot recognize the path.

Rational Synergy solves this problem by stripping the /tmp_mnt prefix from automounted file systems paths. Rational Synergy also strips any prefix set using the AUTOMOUNT_FIX environment variable.

Indirect automounter maps

If you use an indirect automounter map, you might have to set the environment variable AUTOMOUNT_FIX in the environments of all users. You can use the AUTOMOUNT_FIX environment variable to resolve any potential automounter-related problems. If AUTOMOUNT_FIX is set to a string, Rational Synergy strips that string from the beginning of any path. For example, if AUTOMOUNT_FIX is not set, the default is to strip /tmp_mnt.

Setting AUTOMOUNT_FIX is appropriate only if both of the following are true:

You might need to create symbolic links on some machines to ensure that files on the automounted file system are accessible on all machines by the same path. If you do not know how to create symbolic links, see your automounter documentation.


Feedback