REXEC(3)                                                              REXEC(3)



NAME
       rexec - return stream to a remote command

SYNOPSIS
       rem = rexec(ahost, inport, user, passwd, cmd, fd2p);
       char **ahost;
       int inport;
       char *user, *passwd, *cmd;
       int *fd2p;

DESCRIPTION
       _R_e_x_e_c looks up the host _*_a_h_o_s_t using _g_e_t_h_o_s_t_b_y_n_a_m_e(3N), returning -1 if
       the host does not exist.  Otherwise _*_a_h_o_s_t is set to the standard  name
       of the host.  If a username and password are both specified, then these
       are used to authenticate to the foreign host; otherwise the environment
       and  then the user’s _._n_e_t_r_c file in his home directory are searched for
       appropriate information.  If all this fails, the user is  prompted  for
       the information.

       The  port  _i_n_p_o_r_t specifies which well-known DARPA Internet port to use
       for the connection; the call ‘‘getservbyname("exec", "tcp")’’ (see _g_e_t_‐
       _s_e_r_v_e_n_t(3N))  will  return a pointer to a structure, which contains the
       necessary port.  The protocol for connection is described in detail  in
       _r_e_x_e_c_d(8C).

       If  the  connection  succeeds,  a socket in the Internet domain of type
       SOCK_STREAM is returned to the caller, and given to the remote  command
       as stdin and stdout.  If _f_d_2_p is non-zero, then an auxiliary channel to
       a control process will be setup, and a descriptor for it will be placed
       in  _*_f_d_2_p.   The control process will return diagnostic output from the
       command (unit 2) on this channel, and will also accept  bytes  on  this
       channel  as  being  UNIX signal numbers, to be forwarded to the process
       group of the command.  The diagnostic  information  returned  does  not
       include  remote  authorization  failure, as the secondary connection is
       set up after authorization has been verified.  If _f_d_2_p is 0,  then  the
       stderr (unit 2 of the remote command) will be made the same as the std‐‐
       out and no provision is made  for  sending  arbitrary  signals  to  the
       remote  process, although you may be able to get its attention by using
       out-of-band data.

SEE ALSO
       rcmd(3), rexecd(8C)



4.2 Berkeley Distribution        May 14, 1986                         REXEC(3)