tt_host_file_netfile(3) [hpux man page]

tt_host_file_netfile(library call)										tt_host_file_netfile(library call)

NAME

       tt_host_file_netfile -- map between local and canonical pathnames on a remote host

SYNOPSIS

       #include <Tt/tt_c.h>
       char *tt_host_file_netfile(
       const char *host,
       const char *filename);

DESCRIPTION

       The  tt_host_file_netfile function performs a conversion equivalent to that of the tt_file_netfile(3) function, but performs it on a remote
       host.

       The filename argument is a pathname (absolute or relative) that is valid on the remote host.   Every  component	of  filename  must  exist,
       except for the last component.  The host argument is a name of a remote host.

RETURN VALUE

       Upon  successful  completion,  the  tt_host_file_netfile function returns a freshly allocated null-terminated string of unspecified format,
       which can be passed to tt_netfile_file(3) or tt_host_netfile_file(3); otherwise, it returns an error  pointer.	The  application  can  use
       tt_ptr_error(3) to extract one of the following Tt_status values from the returned pointer:

       TT_ERR_PATH
		 The filename argument is a path that is not valid on the remote host.

       TT_ERR_DBAVAIL
		 The  ToolTalk	database server could not be reached on host, perhaps because the host is unavailable or cannot be reached through
		 the network.

       TT_ERR_DBEXIST
		 The ToolTalk database server is not properly installed on host.

       TT_ERR_UNIMP
		 The ToolTalk database server contacted is of a version that does not support tt_host_file_netfile.

APPLICATION USAGE

       The tt_file_netfile(3), tt_netfile_file(3), tt_host_file_netfile(3) and tt_host_netfile_file(3) functions allow an application to determine
       a  path valid on remote hosts, perhaps for purposes of constructing a command string valid for remote execution on that host.  By composing
       the two calls, paths for files not accessible from the current host can be constructed.	For example, if path /sample/file is valid on host
       A, a program running on host B can use

       tt_host_netfile_file("C", tt_host_file_netfile("A", "/sample/file"))

       to determine a path to the same file valid on host C, if such a path is possible.

       Allocated strings should be freed using either tt_free(3) or tt_release(3).

       The tt_open(3) function need not be called before tt_host_file_netfile.

SEE ALSO

       Tt/tt_c.h - Tttt_c(5), tt_file_netfile(3), tt_netfile_file(3), tt_host_netfile_file(3), tt_open(3), tt_free(3), tt_release(3).

														tt_host_file_netfile(library call)

on(1)							      General Commands Manual							     on(1)

NAME

       on - execute command on remote host with environment similar to local

SYNOPSIS

       | host [command [argument] ... ]

DESCRIPTION

       executes a command on a remote host, using an environment similar to that of the invoking user where:

	      host	specifies the name of the host on which to execute the command.

	      command	specifies the command to execute on host

       If command is not specified, starts a shell on host.  argument ...  is a list of arguments for command.

       The  user's environment variables are copied to the remote host, and the file system containing the user's current working directory is NFS
       mounted on the remote host (see nfs(7)).  The command is executed on the remote host in the user's current working directory.

       Commands using relative path names that reference file system objects within the user's current working file system have the same  behavior
       as  running  the command on the client.	The behavior of commands using relative path names that cross the file system boundary or commands
       using absolute path names depends on the organization of the remote host's file system.

       Implicit and explicit use of environment variables may also cause a command's behavior to be dependent on the organization  of  the  remote
       host's file system.  For example, the environment variable usually contains absolute path names.

       Standard input, output and error of the remote command are connected to the appropriate file descriptors on the client.

       The remote execution daemon does not allow to execute a remote command.

       The  signals and are propagated to the remote command.  and are ignored by the remote command.  All other signals are delivered to the com-
       mand.

       In order to execute a remote command, the remote host must be configured to execute (see rexd(1M)).

   Options
       recognizes the following options:

	      Interactive mode.
		      This option is required for commands that must communicate with a terminal such as or Terminal mode changes  are	propagated
		      to the server.  The standard input for an interactive command must be a tty device.  The and options are mutually exclusive.

	      Debug mode.
		      Print  diagnostic messages during startup of the command.  These messages are useful for detecting configuration problems if
		      the command to a specific host is failing.

	      No input mode.
		      This option causes the remote command to get end-of-file (EOF) when it reads from standard input, instead of connecting  the
		      standard	input of the command to the standard input of the remote command.  The option is required when running commands in
		      the background.  The and options are mutually exclusive.

DIAGNOSTICS

       The host name
		 host was not found in the hosts database.

       The host  host is down, unreachable on the network, or not running

       A problem occurred trying to find the user's current working directory
		 (current_dir).

       A problem occurred trying to determine the mount point
		 of the user's current working directory (current_dir).

       The standard input (stdin) of the
		 command with the option is not a tty device.

       Errors that occur on the server
		 server are propagated back to the client.  These messages are documented in the DIAGNOSTICS section of rexd(1M).

AUTHOR

       was developed by Sun Microsystems, Inc.

SEE ALSO

       exports(4), rexd(1M).

																	     on(1)