hostname_map(4)
NAME
hostname_map - tell ToolTalk clients to use a per-host alternative rpc.ttdbserverd(1m)
SYNOPSIS
hostname_map
DESCRIPTION
A ToolTalk hostname_map tells ToolTalk clients to use host A’s rpc.ttdbserverd(1m) as a proxy for host B. In this way, ToolTalk databases can be created for filesystems exported from hosts (like host B) that for whatever reason do not run rpc.ttdbserverd(1m).
The hostname_map file is called "hostname_map" and resides in the same directories as the ToolTalk types databases; see tt_type_comp(1). If $TT_HOSTNAME_MAP is set, it is used in place of $HOME/.tt/hostname_map.
ToolTalk clients read the hostname maps when the ToolTalk client library is initialized in e.g. tt_open(3). ttsession reads the hostname maps upon startup and rereads them if it receives signal USR2.
Format rules
The format rules for a hostname_map are:
1. Any line beginning with a "#" or white-space and a "#" is a comment.
2. Blank lines are comments.
3. Words are delimited by white space.
4. The first word in a non-comment line is the host name from which to map.
5. The second word in a non-comment line is the host name to which to map.
ENVIRONMENT
TT_HOSTNAME_MAP
If $TT_HOSTNAME_MAP is set, it is used in place of $HOME/.tt/hostname_map.
TTPATH
A colon-separated list of directories in which to seek hostname_maps. See tt_type_comp(1).
EXAMPLES
This example maps "mainframe1" to "sparcstorage":
# rpc.ttdbserverd cannot run on filesystems
# exported from mainframe
mainframe1 sparcstorage
SEE ALSO
rpc.ttdbserverd(1m), ttsession(1), tt_type_comp(1), tt_open(3), partition_map(4)
SunOS 5.5/SPARC — Last change: 28 March 1995