HP LCS60 manual Symbolic Links

PUSH (1C) PUSH

Long Names

If the target machine is not a SVR4 implementation and the source machine transfers a file with a name greater then 14 characters, the name will usually be truncated to 14 characters. Note: A few pre- SVR4 implementations support long file names but the push com- mand has no way of knowing if these systems do or do not. The local side will warn the user for each file name that may be trun- cated.

Symbolic Links

Files of type symbolic link will be preserved unless the '– L' option is used or the target machine does not support symbolic links. A transferred symbolic link will be identical to the source file; it may, however, have a different context in the target environment. If the '– L' option is used or the target machine does not support sym- bolic links, the source machine will follow symbolic links with the following behaviors: The symbolic link will be treated as if it were the file type of the file pointed to. If the file does not exist or the user does not have permission to access the file, no transfer will take place and the source machine will issue a warning. If, in fol- lowing a path that contains a symbolic link that points to a direc- tory, the source machine finds a directory that has already been transferred, it will not transfer it a second time. The source machine, however, will always transfer directories in a path that does not contain a symbolic link even if that directory has already been transferred while following a path that does contain a sym- bolic link. In both cases the source machine will warn the user for every affected directory.

The push and pull(1C) commands invoke the pupu program (/opt/dk/bin/pupu) on the remote system to handle the remote end of all file transfers. If the srvtab(4) file on the remote system invokes the pupu program with the ´– r´ option, file transfers will be restricted to/from the home directory tree on the remote system by disallowing all paths that begin with a leading ´/´ or that contain an embedded

´..´ specification. In this restricted mode, only transfers containing PATHs relative to the HOME directory will be accepted.

Multiple Interfaces

If multiple interface boards are installed on the originating host the push com- mand will use the default processing to select the interface for the out-going call. See dkdial(3X) and authorize(1M) for more information.

WARNINGS

If the source host is identical to the target destination and the source directory is identical to the target directory, then the push command will overwrite filename and its contents may be destroyed.

The modification times are preserved on transferred files as long as they are ear- lier in relative time (i.e. seconds since the 00:00:00 GMT, January 1, 1970, epoch) than the current relative time on the local machine. If the modification time for a file would date that file in the future on the local machine, the current time on the

E-38 Issue 3