Remote Command Protocol Class Library  
 

Execute commands on a server or establish an interactive terminal session.

Reference

Library Information

Class Name CRshClient
File Name CSRSHAV7.DLL
Version 7.2.7210.1845
LibID 886F0B3C-D077-4FF4-8FC5-0D35EBFD82C4
Import Library CSRSHAV7.LIB
Dependencies None
Standards RFC 1282

Overview

The Remote Command protocol is used to execute a command on a server and return the output of that command to the client. This is most commonly used with UNIX based servers, although there are implementations of remote command servers for the Windows operating system. The library supports both the rcmd and rshell remote execution protocols and provides methods which can be used to search the data stream for specific sequences of characters. This makes it extremely easy to write Windows applications which serve as light-weight client interfaces to commands being executed on a UNIX server or another Windows system. The library can also be used to establish a remote terminal session using the rlogin protocol, which is similar to the Telnet protocol.

This class library should not be used when connecting to a server over the Internet because the user credentials are sent as unencrypted text. For secure remote command execution and interactive terminal sessions, it is recommended that you use the SocketTools Secure Shell (SSH) class instead.

Requirements

The SocketTools Library Edition libraries are compatible with any programming language that supports calling functions exported from a standard dynamic link library (DLL). If you are using Visual C++ 6.0 it is required that you have Service Pack 6 (SP6) installed. It is recommended that you install all updates for your development tools and have the current Windows SDK installed.

This library is supported on Windows XP, Windows Server 2003, Windows Vista, Windows 7 and Windows Server 2008. If you are using Windows XP, it is required that you have Service Pack 3 (SP3) installed. It is recommended that all service packs and critical updates to the Windows operating system be installed.

This product includes both 32-bit and 64-bit libraries. Native 64-bit CPU support requires the latest 64-bit version of Windows XP Professional, Windows Server 2003 or later versions of the Windows operating system.

Distribution

When you distribute your application that uses this library, it is recommended that you install the file in the same folder as your application executable. If you install the library into a shared location on the system, it is important that you distribute the correct version for the target platform and it should be registered as a shared DLL. This is a standard Windows dynamic link library, not an ActiveX component, and does not require COM registration.