Requirements for File-Name Mapping

To correctly perform this file-name mapping, one of the following must be true:

• The mount command is used to statically mount file systems. These types of static mounts are typically configured in a file such as /etc/checklist, /etc/mnttab, or /etc/filesystems.

  For file-name mapping to work correctly between systems, file system mounts must use consistent host names. If a host is known by several names (for example, aliases, or if the host has more than one LAN address that are known by different names), you must use the same name and form of the name for all mounts.

• Or, the automounter is used to mount file systems at the default /net mount point.

• Or, the automounter is used to mount file systems at a location other than /net and the DTMOUNTPOINT environment variable is set to indicate the mount point. See the next section, "Setting a Value for DTMOUNTPOINT".

  For information about the automounter, see the automount(1M) man page.

Setting a Value for DTMOUNTPOINT

You must set the DTMOUNTPOINT environment variable if both of the following conditions are true:

• The automounter is used to mount file systems.

• And, remote file systems are mounted at a location other than /net.

  DTMOUNTPOINT must be set for processes, including:

• The user's desktop processes that are automatically started when the user logs in, such as the Workspace Manager (dtwm) and File Manager (dtfile)

• System processes such as rpc.ttdbserver and dtspcd that are started by mechanisms such as inetd

• Applications that are started by the desktop on local or remote systems

• Applications that are started by the user from a shell command line

  To set DTMOUNTPOINT for these processes:

1. Edit the file /etc/inetd.conf:

2. Find the dtspcd entry and add:

   -mount_point mount_point

3. Find the rpc.ttdbserver entry and add:

   -m mount_point

   For example if the automounter is being used with a mount point of /nfs, the entries in /etc/inetd.conf are:

   dtspc stream tcp nowait root /usr/dt/bin/dtspcd \ /usr/dt/bin/dtspcd -mount_point /nfs rpc stream tcp wait root /usr/dt/bin/rpc.ttdbserver \ 100083 1 rpc.ttdbserver -m /nfs

4. Perform the procedure on your system that rereads /etc/inetd.conf. For more information, see the inetd(1M) man page.

5. Set DTMOUNTPOINT such that its value is inherited by user logins.

   This can be done by setting the variable in /etc/dt/config/Xsession.d. For more information on setting environment variables, see "To Set Environment Variables".

Configuring the Subprocess Control Daemon

The desktop subprocess control (SPC) service provides client/server command execution.

The desktop subprocess control daemon (dtspcd) is used by the desktop to launch remote applications. It is an inet daemon that accepts requests from remote clients to execute commands. For more information on how to configure inet daemons, see the inetd.conf(1M) man page.

The desktop action invocation library uses the SPC service to invoke remote actions.

To Configure dtspcd

• Confirm that dtspc is properly registered in both /etc/services and /etc/inetd.conf.

See the dtspcd(1M) man page.

SPC Security

Authentication for the subprocess control service is based on file system authentication. The dtspcd must have access to an authentication directory that is also mounted by all SPC client systems.

By default the dtspcd authentication directory is the user's home directory. However, you can configure the dtspcd to use a different location by setting the -auth_dir option in the /etc/inetd.conf directory. See the dtspcd(1M) man page for more information.

Because SPC authentication is based on file system authentication, the SPC service is only as secure as your distributed file system. If you are using the desktop in a network where you do not trust the distributed file system, you may wish to disable the dtspcd. To disable the dtspcd, comment out the dtspc entry in /etc/services.

Configuring Environment Variables for Remote Execution

When the desktop uses an action to start an application on a remote system, the user's environment variables are copied to the remote system and placed in the environment of the application.

By default, some of the environment variables are altered before they are copied to the remote system. You can configure both the action invocation component and the subprocess control service of the desktop to perform additional environment variable processing before the variables are placed into the application's environment.

For more information on the default configuration and how to modify it, see the dtactionfile(4) and dtspcdenv(4) man pages.

Configuring the ToolTalk Database Server

One component of ToolTalk is the ToolTalk database server, /usr/dt/bin/rpc.ttdbserver.

The ToolTalk database server is used by the ToolTalk messaging service and for file-name mapping. It is usually registered in /etc/inetd.conf when the desktop is installed and needs no additional configuration.

For more information on the ToolTalk database server and its configuration options, see the rpc.ttdbserver(1M) man page.