Note: This article is strictly for beginning UNIX® users and administrators. More experienced UNIX users will likely already know several ways of accomplishing this task.

Introduction: Executing a remote command on multiple computers

When you hear someone discussing a shell, do you know what it means? Basically on any UNIX machine, you open a terminal session where you type your commands to perform an activity, such as useradd username, passwd password, system-config-printers, and so on. This shell is local to your machine, so whatever command you execute performs activity on your local machine.

However, what if you want to execute a command on a set of machines, such as setting the date on all the machines on the network. One way is to log in individually to each machine and execute the date command. A better way would be to set it automatically, where you log in to a server and have that server using rsh set the date on the rest of the machines serially. To set the date remotely, you need tools like Secure Shell (SSH) and remote shell (rsh) installed on your machines. Usually, when you try to access the remote machines, you will be prompted for a password to make sure that you are an authorized user. However, you can configure SSH and rsh in your environment to bypass password verification. In this article, you will concentrate on how to configure rsh in your environment. In Part 1, SSH was discussed.

Back to top

Hardware, software, and setup

Use the following hardware and software to perform the tasks described in this article:

• IBM System p™ and System x™ servers, such as System p520 and System x345
• Red Hat Enterprise Linux® Version 4.0 Update 3 (RHEL Version 4.0 Update 3)

Now follow these steps:

1. Install RHEL Version 4.0 Update 3 on all your machines in the environment, such as node1.my.com, node2.my.com, and node3.my.com, as shown in Figure 1. (Note: Code listings mentioned here appear after all the instructions in the list.) I used Base RHEL4 for this testing.
2. Make sure rsh-server-0.17-25.1 is installed on all your machines, as shown in Listing 1.
3. If you already have rsh-server-0.17-25.1 installed, you will find rsh, rlogin, and rexec files in the /etc/xinetd.d/ folder on your machines, as shown in Listing 2. (Note: The rsh, rlogin, and rexec services are disabled by default).
   
4. In case you don't have rsh-server-0.17-25.1 installed, install it using RHEL4 CDs using the command, as shown in Listing 3. You can also use the #system-config-packages command to install the rsh-server rpm.

     #rpm -qa|grep rsh-server
				rsh-server-0.17-25.1
			

     /etc/xinetd.d

     -rw-r--r--  1 root root 361 Nov 23  2004 rexec
     -rw-r--r--  1 root root 378 Nov 23  2004 rlogin
     -rw-r--r--  1 root root 431 Nov 23  2004 rsh


     #cat /etc/xinetd.d/rsh 
			
     service shell
     {
     socket_type	= stream
     wait		= no
     user		= root
     log_on_success	+= USERID
     log_on_failure 	+= USERID
     server		= /usr/sbin/in.rshd
     disable		= yes
     }


     #cat /etc/xinetd.d/rogin

     service login
     {
     socket_type	= stream
     wait		= no
     user		= root
     log_on_success	+= USERID
     log_on_failure 	+= USERID
     server		= /usr/sbin/in.rlogind
     disable		= yes
     }

     #cat /etc/xinetd.d/rexec 

     service exec
     {
     socket_type	= stream
     wait		= no
     user		= root
     log_on_success	+= USERID
     log_on_failure 	+= USERID
     server		= /usr/sbin/in.rexecd
     disable 	= yes
     }
			

     #rpm -ivh rsh-server-0.17-25.1.i386.rpm
			

Back to top

Configuring for root and standard users

You have the following two types of configurations to consider:

• Root user
• Standard user, in this case, myuser

Let's first consider configuring rsh for the root user. To configure the root user, follow these steps:

1. Log in as root
2. Enable the rsh, rlogin, and rexec services on all the machines, as shown in Listing 4. (Note: Code listings mentioned here appear after all the instructions in the list.) You can use #system-config-services or #ntsysv to enable the services. If you are an expert, you can manually make the changes in the required files.
3. Create a file /root/.rhosts on all the machines, as shown in Listing 5. Include all the machine names in this file where you want to execute a command without being prompted for a password.
4. Append rsh and rlogin entries in the /etc/securetty file, as shown in Listing 6.
5. After making the above changes, restart the xinetd service on all the machines, as shown in Listing 7.
6. Test your environment by executing the #rsh node3 date command. Doing so should let you see the date output from node3.my.com, as shown in Listing 8. In case you want to log in to node3, then execute #rsh node3, as shown in Listing 9.

     #cat /etc/xinetd.d/rsh 
			
     service shell
     {
     socket_type	= stream
     wait		= no
     user		= root
     log_on_success	+= USERID
     log_on_failure 	+= USERID
     server		= /usr/sbin/in.rshd
     disable		= no
     }


     #cat /etc/xinetd.d/rogin

     service login
     {
     socket_type	= stream
     wait		= no
     user		= root
     log_on_success	+= USERID
     log_on_failure 	+= USERID
     server		= /usr/sbin/in.rlogind
     disable		= no
     }

     #cat /etc/xinetd.d/rexec 

     service exec
     {
     socket_type	= stream
     wait		= no
     user		= root
     log_on_success	+= USERID
     log_on_failure 	+= USERID
     server		= /usr/sbin/in.rexecd
     disable 	= no
     }
			

     #cat /root/.rhosts 
     node1.my.com	
     node2.my.com	
     node3.my.com	
			

\

     #cat /etc/securetty
     rlogin
     rsh
     console
     vc/1
     vc/2
     ..
     ..	
			

     #service xinetd stop/start OR #service xinetd restart
			

     node1.my.com>#rsh node3 date
     Mon Aug 28 17:44:48 IST 2006
			

     node1>#rsh node3
     node3>#
			

Next, configure rsh for any standard user, in this case, myuser. To do this, let's make the assumption that the username, myuser, exists on all the nodes. You want to test the situation where myuser is able to execute the command on a remote machine without being prompted for a password.

1. Log in as root.
2. Enable the rsh, rlogin, and rexec services on all the machines, as shown in Listing 4.
3. Create a file /etc/hosts.equiv, as shown in Listing 10.
4. Next restart the xinetd service, as shown in Listing 7.
5. Log in as myuser, as shown in Listing 11.
6. Test your environment by executing the $rsh node3 date command. Doing so should return the date output from node3.my.com, as shown in Listing 12.

     #cat /etc/hosts.equiv
     node1.my.com	myuser
     node2.my.com	myuser
     node3.my.com	myuser
			

     node1>#su - myuser
     node1>$
			

     node1>$rsh node3 date
     Mon Aug 28 17:49:28 IST 2006
			

Back to top

Conclusion: Using rsh to save time

In this article, you learned how to configure rsh in your environment so that you can perform activities more easily and quickly. This not only saves time, but it also gives you flexibility to perform activities one at a time without being prompted for a password on a large number of machines. Part 1 discussed how to configure SSH, another way of executing sequential commands across your cluster environment without being prompted for a password.

Resources

Learn

• "Run commands sequentially across a cluster from a UNIX server, Part 1" (developerWorks, August 2006): Learn how to configure Secure Shell (SSH) on IBM System p and System x computers.
  
  
• About RSH Web site: Visit this site to find out more about rsh.
  
  
• Remote Shell: All you need to know about remote shell.
  
  
• HOWTOs on Linux: Visit this site to learn more about Linux, or solve an issue.
  
  
• IBM Systems: Want more? The developerWorks IBM Systems zone hosts hundreds of informative articles and introductory, intermediate, and advanced tutorials.
  
  
• developerWorks technical events and webcasts: Stay current with developerWorks technical events and webcasts.
  
  

Get products and technologies

• IBM trial software: Build your next development project with software for download directly from developerWorks.
  
  

Discuss

• Participate in the IBM Systems forums, developerWorks blogs, and get involved in the developerWorks community.
  
  

About the author

Harish has been with IBM since 1998 and has 14 years of experience. During his last eight years with IBM, he has spent five years at the India Research Lab and one year at the IBM T.J.Watson Research Center. Harish has been leading the Linux Center of Competency in Bangalore, India for the past two years. You can contact him at hchauhan@in.ibm.com.

Comments

Back to top

Trademarks  |  My developerWorks terms and conditions

Table of contents

• Introduction: Executing a remote command on multiple computers
• Hardware, software, and setup
• Configuring for root and standard users
• Conclusion: Using rsh to save time
• Resources
• About the author
• Comments

Local resources

• IBM Innovation Center - Austin, TX
• IBM Innovation Center - Chicago, IL
• IBM Innovation Center - Dallas, TX
• IBM Innovation Center - San Mateo, CA
• IBM Innovation Center - Waltham, MA
• Technical Briefings in North America

My developerWorks community

Dig deeper into AIX and UNIX on developerWorks

Cloud computing for developers

Virtual workshop: Learn how to build a cloud infrastructure and develop/deploy cloud-based applications. (6-8 Apr 2010)

Special offers