Advanced RCCMD Settings

Event Log File

Specify how many KB the log file may become before RCCMD starts to overwrite the oldest entry. The following scheme is followed:

Entry 1 -> This entry will be removed.

Entry 2

Entry 3

Entry 4 -> This entry will be added

RCCMD log files will be read from top. The first entry is generally the oldest available entry and the most recent entry at the bottom of the event list. 

RCCMD Bindings

RCCMD Bindings is a sophisticated tool that helps you to limit traffic. Since this setting deeply affects your network setting, it should be used with caution. The bindings allow forcing RCCMD to listen on a specific network card. In case multihoming is in use, the listener can be configured to a specific IP address within one network card.  As an example, this will be used if there is a necessity to divide the network logically into a production network and an infrastructure network via VLAN:

In this example scenario, two or more network adapters can be installed. Binding RCCMD to one specific network card will prevent users from accessing the RCCMD client and accidentally shut down a server — this is only possible via devices that are located in VLAN 3 or have been properly enabled via a router.

Another scenario is the so-called “multihoming”:

It is not absolutely necessary for modern network devices that an IP address is firmly linked to one network interface. In fact, multiple IP addresses can be connected via a network interface - they share hardware, but otherwise form self-contained instances. 

As an example, this could be a web server that manages different websites with a unique IP address: the server is connected by a router that determines between incoming signals and signals provided by local network. Bindings will instruct RCCMD to listen for incoming RCCMD signals only at a specific IP address that is assigned to the local network only.

Note: These configurations are used in special scenarios. Normally you can leave the setting 127.0.0.1 / local host, port 6003. In that case, RCCMD will listen on all available IP addresses for a valid incoming signal. Since you have defined the valid sender address at the menu Connections, RCCMD will notice the signal but deny execution and log this fact as an invalid RCCMD command.

Message Port

Normally, RCCMD is a background service that is not allowed to show messages on the display. For this purpose, the RCCMD service passes the information to the "Web-If", which is registered as a foreground process and therefore authorized to interact with a user and trigger or initiate foreground processes.

Special function: Running a job as interactive user

This function allows RCCMD to interact with the system as a foreground process with the rights of the currently logged-in user. The operating condition is that at least one user must be logged in to execute a command. Which commands and scripts can be executed depend on the system rights of the according user.

RCCMD License

Each RCCMD installation requires a corresponding license. If you do not have a license at hand when starting, a 30-day demonstration license will start automatically. After that, RCCMD will stop until you have entered a valid license.

Please note that RCCMD clients in the network coordinate with each other: If you have issued a duplicate license, only the first installation claiming the license will run. The other clients will disable RCCMD service with a license fraud message in the event log.