[start | stop]
rconfig helps to configure the MKS and Windows-specific features of the PTC MKS Toolkit version of the rshd and rexecd services. These services are based on traditional UNIX daemons and many basic configuration settings are handled using traditional UNIX methods (for example, the ~/.rhosts and ROOTDIR/etc/hosts.equiv files).
The service argument to rconfig is either rshd or rexecd, indicating which service rconfig is to work with.
When the second argument is status, rconfig enters status mode. In status mode, rconfig does not modify the selected service, but instead returns information about that service.
When the second argument is start or stop, rconfig attempts to start or stop the specified service.
When not in status mode, rconfig accepts the following options:
tells the service to fail when the local user does not exist (the default).
tells the service to attempt to connect as a domain user when the local user does not exist.
allows multiple connections to the service (the default).
allows allows only a single connection to the service.
writes only error messages to the event log (the default).
writes all connections to the event log.
When in status mode, rconfig accepts the following options:
displays how the service responds when the local user does not exist.
displays the current running status of the service.
When a service is STOPPED or UNINSTALLED, you can start it with the rconfig start argument.
When a service is RUNNING, you can stop it with the rconfig stop argument.
displays Single when the service accepts only a single connection and Multiple when the service accepts multiple connections.
displays the status of the event logging. If all connections are being logged, rconfig displays Logging; if they are not, rconfig displays NoLogging.
When no options are specified in status mode, rconfig
behaves as if
Possible exit status values are:
rconfig is provided as a KornShell executable script. MKS cannot be responsible for proper functionality of this code if you alter the rconfig.sh file in any way.
Windows Server 2012. Windows 8.1. Windows Server 2012 R2. Windows 10. Windows Server 2016. Windows Server 2019.
PTC MKS Toolkit for System Administrators
PTC MKS Toolkit for Developers
PTC MKS Toolkit for Interoperability
PTC MKS Toolkit for Professional Developers
PTC MKS Toolkit for Professional Developers 64-Bit Edition
PTC MKS Toolkit for Enterprise Developers
PTC MKS Toolkit for Enterprise Developers 64-Bit Edition
MKS Toolkit Connectivity Solutions Guide
PTC MKS Toolkit 10.3 Documentation Build 39.