Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
International Rescue Committe

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 51 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       rexec [ -abcdhns -l username -p password ] host command


       Rexec  calls  the  rexec(3) routine to act as a client for
       the remote host's rexecd(8) server.

       It asks that ``command'' be  run  on  the  host  computer,
       using  username/password  authentication. See rexec(3) and
       rexecd(8) for details of the protocol.


       Rexec accepts several options, but only three  are  likely
       to be very useful:

       -l username

              Set the log-in name on the remote host to username.

       -p password

              Provide the password for the remote  account.   The
              command  line  argument will be blanked after being
              parsed, to prevent it from being seen  with  ps(1).
              However,  it  is  still not very secure to type the
              password on the command line.   In  particular,  be
              sure that the shell's history file is protected.

       -n     Explicitly  prompt  for  name and password, even if
              provided in the environment,  in  the  $HOME/.netrc
              file,  or in the environmental variables REXEC_USER
              and REXEC_PASS.

       Other options  that  might  be  useful  with  non-standard
       remote exec daemons, or to debug connections:

       -a     Do  not  set  up  an auxiliary channel for standard
              error from command; the remote standard  error  and
              output are then both returned on the local standard
              output.  By default, rexec  asks  that  a  separate
              channel  be  set  up for diagnostic output from the
              remote command.

       -b     Use signal handling as in  BSD  rsh(1).   Only  the
              signals  SIGINT, SIGQUIT, and SIGTERM are echoed to
              the remote process.   They  do  not  remain  raised
              locally,  so  rexec waits for the remote command to
              shutdown its side of  the  socket.   Also,  CNTRL-Z
              will  only  suspend  execution  locally--the remote
              command may continue to run.

       -c     Do not close remote standard input when local stan­


       Rexec(1) searches for the username  and  password  in  the
       following order:

              1.  If  -n  is  given on the command line, the user
              will always be prompted for both, even if they  are
              also given on the command line.

              2. The command line will be parsed

              3.  If  the  environmental  variables REXEC_USER or
              REXEC_PASS are defined, they will define the  user­
              name or password.

              4.  The  $HOME/.netrc  file  will be searched.  See
              ftp(1) for a description of this file's format.

              5. Finally, the user will be prompted if either the
              username or password remains undefined.


       Users of this command should be aware that rexec(3) trans­
       mits their password to the remote  host  clear  text,  not
       encrypted.   If  the  network  is not secure to the remote
       host, the password can be comprimised.


       Without the -b option, all signals which  can  be  handled
       are  echoed  to  the remote process.  Afterwards, however,
       they remain raised in the local process.  Typically,  this
       means that rexec(1) will exit after receiving a fatal sig­
       nal, even if the remote process has arranged to handle  or
       ignore it.

       Differing  operating systems use differing signal numbers;
       for example AIX and SunOS use 18 for SIGTSTP  (^Z),  while
       Linux  uses 20.  Therefore, it may have a different effect
       remotely than locally.  In particular, typing  CNTL-Z  may
       not suspend the execution of the remote process.


       rexec othermachine cat ">remote_file; date" <local_file

       will send local_file to the othermachine as remote_file.


       Please send bug reports, system incompatibilities, and job
       offers to the author.

                        February 14, 1997                REXEC(1)
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.08 Seconds