Home
Search all pages
Subjects
By activity
Professions, Sciences, Humanities, Business, ...
User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...
Text Strings
Conversions, tests, processing, manipulation,...
Math
Integer, Floating point, Matrix, Statistics, Boolean, ...
Processing
Algorithms, Memory, Process control, Debugging, ...
Stored Data
Data storage, Integrity, Encryption, Compression, ...
Communications
Networks, protocols, Interprocess, Remote, Client Server, ...
Hard World Timing, Calendar and Clock, Audio, Video, Printer, Controls...
File System
Management, Filtering, File & Directory access, Viewers, ...
|
|
|
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
Others
REXEC(3) OpenBSD Programmer's Manual REXEC(3)
NAME
rexec - return stream to a remote command
SYNOPSIS
int
rexec(ahost, int inport, char *user, char *passwd, char *cmd, int *fd2p);
DESCRIPTION
This interface is obsoleted by krcmd(3). It is available from the com-
patibility library, libcompat.
The rexec() function looks up the host *ahost using gethostbyname(3),
returning -1 if the host does not exist. Otherwise *ahost is set to the
standard name of the host. If a username and password are both speci-
fied, then these are used to authenticate to the foreign host; otherwise
the environment and then the user's .netrc file in his home directory are
searched for appropriate information. If all this fails, the user is
prompted for the information.
The port inport specifies which well-known DARPA Internet port to use for
the connection; the call `getservbyname("exec", "tcp")' (see
getservent(3)) will return a pointer to a structure, which contains the
necessary port. The protocol for connection is described in detail in
rexecd(8).
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 fd2p is non-zero, then an auxiliary channel to a
control process will be setup, and a descriptor for it will be placed in
*fd2p. 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 au-
thorization failure, as the secondary connection is set up after autho-
rization has been verified. If fd2p is 0, then the stderr (unit 2 of the
remote command) will be made the same as the stdout 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(8)
HISTORY
The rexec() function appeared in 4.2BSD.
OpenBSD 2.6 June 4, 1993 1
Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts Institute of Technology, Free Software Foundation, FreeBSD Inc., and others. |
(Corrections, notes, and links courtesy of RocketAware.com)
FreeBSD Sources for rexec(3) functions
Up to: Remote Process Communication - Methods of communicating to remote processes. Remote Procedure Calls, sockets, data format translation, et al
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
Others
Rapid-Links:
Search | About | Comments | Submit Path: RocketAware > man pages >
rexec.3/
RocketAware.com is a service of Mib Software Copyright 1999, Forrest J. Cavalier III. All Rights Reserved. We welcome submissions and comments
|