NETUNAM(1) — Series 300, 500, and 800 Only

NAME

netunam − establish access rights on a remote computer

SYNOPSIS

netunam network_special_file userID:password

DESCRIPTION

Netunam is a Remote File Access (RFA) command that allows you to access remote files and directories on remote systems. Netunam establishes access rights on remote computers where the files and directories you want to access reside. Once you have established access rights using netunam, you can access the file system on the remote computer as though it were appended to your local file system.

Netunam allows you to access files and directories on remote HP 9000 Series 300, 500 and 800 systems with standard HP-UX commands and calls. A process can have access to a maximum of 20 remote nodes at one time. Refer to the Using Network Services (NS)/9000 Series 800 manual (for the Series 800 systems), Using Network Services manual (for Series 300 systems) and the NS/9000 LAN User’s Guide (for Series 500 systems) for a list of the calls and commands that are supported with RFA.

After a process executes netunam successfully, its access rights on the remote node remain valid until the process terminates, the process issues netunam with the same remote system but with a different login, or the process terminates its access rights explicitly by executing netunam with a null login. For example:

netunam /net/PC_Design1 ""

Series 500 computers have no limitations on the number of connections per process, and consequently have no command to free connections.

Your current working directory is not altered after a netunam command is executed; it is still your local current working directory. Because your working directory is local, the path name that you use to specify a remote file must be preceded by the name of the network special file that references the computer where the file resides. The path name itself must be an absolute path name that is no more than 26 directory or file names long. RFA between Series 800 computers with HP-UX version A.02.00 or later allows path names up to 1023 characters long, with file names of up to 255 characters each.

You can avoid specifying the network special file and an absolute path name by changing your working directory to a remote working directory. This can be done using the cd command. For example, if your network special file is “PC_Design1” and you want to use the directory “/tests/drill” at the remote system, you would type:

cd /net/PC_Design1/tests/drill

The path name to the remote working directory must be an absolute path name. If you want to change from a local working directory to the root directory of a remote system, the path name must end with the characters slash and dot (/.). Omitting the slash and the dot, as in “/net/PC_Design1”, does not work because “/net/PC_Design1” is the path to a network special file, not to the remote root directory. Including the slash (/) but not the dot will result in an error.

When your working directory is a directory on a remote file system, you cannot use the command cd / to move to the remote root directory. This command will place your working directory at the local root. To reach the remote root directory from a remote working directory, you can use the command cd .. as many times as necessary to move up the file system to the root, one directory at a time. Once you reach the root of a remote file system, the command cd .. has no effect. It cannot be used to move back to the local file system.

Parameters

network_special_file is a relative or absolute path name indicating the location of the network special file that references the computer you want to access. A network special file is a file on your local computer that acts as a pointer from your local file system to the file system at a particular remote node. There must be one network special file for each remote system that you want to access with RFA. Your node manager creates network special files with the mknod command when nodes are initialized. You should consult your node manager to determine the names and location of the network special files on your system before using netunam. The permission bits on network special files are not checked when you execute a netunam command.

userID:password is the login name and password for the remote computer referenced by the network special file specified in network_special_file. userID:password must be a valid entry in the remote computer’s /etc/password file. It may consist of up to 68 characters, including the colon and password. The colon and password need not be specified if no password exists for the login. If the colon is specified but the password is omitted, the system will prompt you for the password with the local echo turned off if a password exists for the user ID. The access rights associated with the login name and password determine your access rights on the remote file system.

EXAMPLES

In the first example, the current working directory is “/net”, the directory that contains the network special file “Admin”.

netunam Admin jim:secret

In the next example, the current working directory is the root directory and the network special file is “Admin”.

netunam net/Admin jim:secret

In the third example, an absolute path name to the network special file “Lab” is given.

netunam /net/Lab jim:secret

In the last example, the password is omitted and a colon is specified so that they system will prompt for the password with the echo turned off.

netunam /net/Lab jim:
password :

WARNINGS

You can not use netunam to reach a node through a gateway. Executing pwd from a remote directory does not return the path of the remote computer.

You must have read permission to execute a file through RFA on an NFS mounted disk. For example,

mount B:/users/foo
netunam /net/A

/net/A/users/foo/<executable> must have read and execute permission for this to work.

Your must own a file to be able to modify the access times using utime(2) or a program that uses utime(2).

DEPENDENCIES

Implemented on the Series 300, 500, and 800 only.

Museum

Related Articles