ends in a slash character, it will be interpreted as the name of a directory. In
this case, the destination file will be placed in this directory and will have the
same name as the local file. However, if the remote pathname is the pathname
of a directory on the remote system and does not end in a slash, then FTP will
attempt to overwrite the directory and file transfer will fail.
II. RCP - As in the case of FTP, the remote pathname is optional, if it is omitted,
the file will be copied to the user’s home directory on the remote system and the
remote file will have the same name as the local file. If the remote path is
specified, it must be relative to the user’s home directory on the remote system.
If the remote pathname is the pathname of a directory, the file will be sent to
that directory and will have the same name on the remote system that it has on
the ASM.
III. UUTO - The remote pathname is not specified for UUTO. If the file transfer
mechanism is chosen to be UUTO, then this field is ignored.
2.12.7.4.5 Examples
The following configuration file will send the automation results file to user spacely on
machine space with IP address space.sprockets.com:
ftp
space.sprockets.com
spacely
/home/spacely/rje/results.out
Alternatively, the IP address can be given explicitly (for example, 555.1.21.2.001). The
path name of the destination on the machine space will be
/home/spacely/rje/results.out.
This configuration file will send the results to the same destination as in the previous
example using RCP instead of FTP:
rcp
space.sprockets.com
spacely
rje/results.out
Note that in this case the path name is specified relative to the remote user’s home
directory.
To send the results file to the same user using UUTO, the configuration file would
look like:
uuto
space
spacely
The remote pathname does not apply to UUTO. The name of the remote system must
be given as it appears on the list of systems known to UUTO.
2.12.7.5 File Transfer Methods
Before using any of the file transfer methods, certain files must be set up on the ASM
or the remote Host. A brief description of these files is provided here. Further details
can be found in the Solaris documentation.
5ESS
®
SWITCH DISTINCTIVE REMOTE MODULE 235-200-150
Feburary 2007
Page 2-66 Issue 3.00O
To Next Page
Loading...
Need help?
General