Client Configuration on Linux

Top  Previous  Next

You can configure the Linux client using any text editor, by editing the cp20c.ini file found in your local configuration.  To see where this file is, you must be logged in as the user who will run the program, and type:

 

cp20c -settings

 

To edit this file using the default "vi" text editor, type:

 

cp20c -config

 

The cp20c.ini file is a text file structured with connection profile sections prefixed with a [profilename] header.  Within each section are name=value lines where you specify the server and login information, and optionally some addition settings.  There is one required section, headed with [settings].  This section stores the default configuration.

 

Another efficient option is to ask the server administrator for a special configuration setup link.  This is a temporary URL that the client can use to automatically set up a connection profile.  You receive this link by email and can copy and paste the command line it includes:

 

cp20c -setup setupURL [ -profile profilename ]

 

If you don't provide a profile name, this command will update the standard "settings" profile.  Otherwise, it will update or create the profile specified.

 

A typical cp20c.ini file might look like this:

 

[settings]

server=https://cp20.example.com:8483

locid=user3@acme

password=12345

logdetail=0

logecho=0

 

[altserver]

server=192.168.1.10

locid=redhatsvr@internal

password=abcdefg

 

 

 

 

Whether configured though the Linux cp20c -config command, or the Windows tool, the same information is required to run the client:

 

Server is the address or hostname CirrusPrint server, along with a :port suffix.  Examples include 192.168.1.99, which will connect to the default 8482 port on the server, or cirrus.acme.com:443 which would connect to port 443.  You may specify a URL prefix of http:// or https:// to indicate if the connection requires SSL.  If not specified this way, the SSL or nossl options are used.
 
Location ID is the location ID used to login to the server.  If the login requires a company ID (i.e. there is no namespace path dedicated to different companies), the company is supplied as a suffix: "@companyID".  For example: john@acme.
 
Password is the password used to login to the server.
 
SSL is enabled to communicate with a server listening with SSL.  If the server is not configured using a http:// or https:// prefix, you can specify the SSL mode using a the SSL or nossl options.
 

One additional feature is that the server administrator can email a special connection link to a remote user.  This link can be used to auto-configure these options.  The email explains how to use the link.