Chapter 3: Starting and Stopping RealProxy

This chapter gives information on starting and stopping RealProxy on both Windows and UNIX-based platforms, and explains the RealProxy license method.

Windows NT

Instructions in this section describe how to start and stop RealProxy running under Windows.

Starting RealProxy Under Windows

RealProxy can be started manually or as a service. You can configure each service to use different configuration files.

Starting RealProxy Manually

You can start RealProxy from the Start menu or from a command line.

To start RealProxy from the Start menu:

On the Start menu, click Programs, then click RealProxy, and finally click RealProxy. This starts the rmserver.exe program. If this is the first time you have run RealProxy, it loads the default configuration file.

Additional Information
The configuration file is described in Chapter 4, "Configuring RealProxy Features".

	Additional Information
The configuration file is described in Chapter 4, "Configuring RealProxy Features".

To start RealProxy from a command line:

Move to the RealProxy Bin directory and type the following at a command line:


rmserver ..\rmserver.cfg

Setting Up RealProxy as a Service

RealProxy on Windows NT can be run as a service. An option during setup configures this automatically. Instructions in this section describe how to add RealProxy to the services list if you did not instruct setup to do so.

You can load different configuration files into different Windows NT registry keys, and connect them to different instances of RealProxy running as separate services. Multiple services of RealProxy can be useful if you want to switch between a production and a test configuration file, for example.

To install RealProxy as a service:

At a command prompt, move to the RealProxy Bin directory.
Import the configuration file you want to use into a specific key in the registry by typing the following:
```
rmserver.exe -import[:key] configuration_file
```
where:

key is the Registry key name you want to use. If you omit it, the default name Config is substituted.

configuration_file is the path and configuration file you want to import. For example, the following command:
```
rmserver.exe -import:Proxy1 ../rmserver.cfg
```
imports all the values in the rmserver.cfg file into the following key of the Windows registry:

HKEY_CLASSES_ROOT\Software\RealNetworks\RealProxy\2.0\Proxy1

Note
You must supply the path to the configuration file. If RealProxy cannot find the configuration file, it will not start.

Tip
You can now start RealProxy using this configuration by typing the following at a command line:
rmserver.exe registry:Proxy1
Install the service by typing the following command at a command prompt:
```
rmserver.exe -install[:ServiceName] "parameters"
```
where:

ServiceName is the name that will appear in the Services dialog box. If you omit ServiceName, RMServer is the default name.

parameters is either the name of the configuration file, or the registry and key name, as entered in Step 2. The format of the registry and key name is registry:key.

Note
The quotation marks surrounding parameters are required.

The next time you start RealProxy from the Services dialog box, it will use the settings specified in parameters, and will be configured to start automatically.

For example, the following command:
```
rmserver.exe -install:NewYorkProxy "Proxy1"
```
installs RealProxy with the service name "NewYorkProxy" and uses the settings in the Proxy1 key.

	Note
You must supply the path to the configuration file. If RealProxy cannot find the configuration file, it will not start.

	Tip
You can now start RealProxy using this configuration by typing the following at a command line: `rmserver.exe registry:Proxy1`

	Note
The quotation marks surrounding `parameters` are required.

To remove any RealProxy from the services list:

At a command prompt, type the following:


rmserver.exe -remove[:ServiceName]

where ServiceName is the optional name of the service. If you omitted a service name when you installed the service, you can omit it here, and RealProxy will use the default name RMServer.

Running Multiple RealProxys on One Windows NT System

You can have configuration files with different names for different configurations of a single RealProxy, or use different names for different RealProxy installations.

You can load configuration files into separate registry keys. Then, run RealProxy as a service, one for each configuration file you loaded.

To import a configuration file into a specific key in the registry:

Follow the instructions in Step 2 of "Setting Up RealProxy as a Service".
Start RealProxy by typing the following:
```
rmserver.exe registry:key
```
where:

key is name you want to use for the configuration. RealProxy places the configuration information in HKEY_CLASSES_ROOT\Software\RealNetworks\RealProxy\2.0\Key.

In the example from Step 2 of "Setting Up RealProxy as a Service", in which the configuration settings are loaded into the "Proxy1" key, the full key name would be HKEY_CLASSES_ROOT\Software\RealNetworks\RealProxy\2.0\Proxy1.

Stopping RealProxy Under Windows

If RealProxy was started from the Start menu or the command prompt, switch to the command window and press CTRL+C.

If RealProxy was started as a service, stop RealProxy through the Services control panel.

UNIX

Instructions in this section describe how to start and stop RealProxy running under UNIX.

Starting RealProxy Under UNIX

Start RealProxy initially with the default configuration file; later, you can create other configuration files and start RealProxy using those.

To start RealProxy under UNIX:

Run the rmserver program. It is located in the bin subdirectory of the RealProxy directory, and the configuration file (rmserver.cfg) is located in the main RealProxy directory.

Move to the bin directory and type the following:


rmserver ../rmserver.cfg

You can run RealProxy in the background by typing the following from the bin directory:


rmserver ../rmserver.cfg &

If you have other configuration files, you can substitute their names for rmserver.cfg and RealProxy will use the settings in the file you name.

To limit RealProxy's memory use:

To limit the amount of memory that RealProxy uses, start RealProxy with the -m parameter:


rmserver ../rmserver.cfg -m 32

where the number after -m can be any amount of memory in megabytes, 32 or greater. Each megabyte of RealProxy memory accommodates 3 to 4 simultaneous connected users. To allow 200 users to connect, specify 50 megabytes of memory instead of 32.

Stopping RealProxy Under UNIX

There are two ways to stop RealProxy under UNIX: with a keystroke and with the kill command.

You can press CTRL+C to stop RealProxy.

To use the kill command, first obtain the process identification number, and then issue the kill command with that process number. The process ID is stored in the rmserver.pid file, which is usually kept in the Logs directory. The PIDPath variable specifies this location.

You can perform both actions with one command. Move to the directory which contains the RealProxy PID file, and type the following:


kill `cat pidfile`

where pidfile is the name of the RealProxy PID file, as shown in the PIDPath variable. The usual name for this file is rmserver.pid.

License Information

The number of client connections available to your RealProxy is determined by information in the license file.

If your RealProxy suddenly allows only 25 connections (rather than the licensed number of 10,000), either your license has expired or RealProxy is unable to start using the settings you've selected. If your license file is incorrect or has expired, contact RealNetworks for a correct license file.

Reading the License File

You can read the file with RealSystem Administrator by clicking About in the left-hand frame. A second browser window appears, displaying the values for your license file. If you have multiple license files, RealProxy will show the values for all of them at once.

You can also read the file with any text editor.

Warning
Do not edit the license file. Any modification to the license file will render it invalid, and RealProxy will not start.

	Warning
Do not edit the license file. Any modification to the license file will render it invalid, and RealProxy will not start.

This file is written in XML format and is stored in the license directory.

The LicenseDirectory variable in the configuration file tells RealProxy where to look for license information. This variable can only be changed by editing the configuration file directly. To learn about the configuration file, see "Configuration File".