Client Usage

Starting

You can start the client with many diffrent parameters. Most of these are optional, but -s and -e are mandatory!

<-s key-server> The keyserver to connect to when getting keyspaces. See the FAQ for a current listing of available servers.
<-e email> Your email address. This is the address you will be registered under, and will receive any related mail to.
[-f socks-server] This is the name of your SOCKS host - e.g. your firewall.
[-u socks-userid] Your User-ID if your SOCKS gatway needs it..
[-w socks-password] The password for the optional authentication with the SOCKS gateway.
[-c blocksperrun] How many blocks the clinen should get from the server on each run. Defaults to 1 block, please change this setting ONLY if you are on a dialup connection! (max 32).
[-t totalruns ] How many times the client will loop.
[-n nicelevel | 100] Specify a nice-level for the client, the drafult is 4. In IRIX specifying 100 will put the client at the absolute lowest priority (b254 in "top"). On Win32 valid vaues are 0-4 (with 4 being IDLE and the default)
[-v verboselevel] Determines the amount of information the client prints on screen. Level 0 prints nothing (quiet). Level 1 Logs only the start and end of each block. Level 2 (default) prints information about network operations. Level 3 prints the progress of testing the keyblock.
[-b breakfile] Tells the client to look for the specified file and use it as a "stop" file. When the file is found, the client will exit upon finishing it's current keyblock. By default the client looks for a file called "stop" or "stop." in the startup-directory (note that this might be differenf from where the binary is placed!)
[-p] This will cause the client to pause and wait for user input before all attempts to communicate with the Key-server. This is to allow dialup-users to wstablish a connection.
[-i] Print the PID of the pricess on STDERR. (Available on UNIX only) This feature is broken in the 1.01 clients, it will be fixed in a later version!
[-m] Perform crypt and performance tests only.

Stopping

There are several ways to stop the client. If it is in the foreground, you can stop it by pressing Ctrl-C. If it is in the background (UNIX systems), you can stop it by issuing a kill command.

As of version 0.96 another feature was added. If you create a file called stop in the client startup directory (note that this may be different from the directory containing the client binary!), the client will stop after the next keyblock is completed. This is the preferred way, since it uses the client power to the most. So if at all possible, please use this method.