Pervasive logo

Prev Advanced Operations Guide Next

Linux Client Configuration Parameters

On the Windows platform, you configure both Pervasive.SQL clients and servers using the Pervasive Control Center. You can use the Pervasive Center also to remotely connect to and configure a Pervasive.SQL Linux server.

On a Linux client, however, configuration is written to the Pervasive registry using either the pvclientcfg script or the psregedit utility, which allows you to display and modify the Pervasive registry.

Using the pvclientcfg Script

To run the script, enter pvclientcfg at a shell prompt. You must be the root user or a member of the group pvsw to save configuration changes. The script displays the current settings and allows you to change the settings by number.

Using the psregedit Utility

This section describes how to use the psregedit utility.

psregedit Syntax 

psregedit 

-key KEYNAME [ -r ] 
-key KEYNAME -value VALUENAME 
-set -key KEYNAME [ -type TYPE ] VALUE 
-set -key KEYNAME -value VALUENAME [ -type TYPE ] VALUE 
-delete -key KEYNAME 
-delete -key KEYNAME -value VALUENAME 
-export -key KEYNAME [ -file FILENAME ] 
-import [ -file FILENAME ]

Description

You can use either slash (/) or backslash (\) as the delimiter for keys.

Note
You must enclose keys within quotes ("). For example, "PS_HKEY_CONFIG/Software/Pervasive Software". Otherwise, spaces are interpreted as the end of your key.

Specifications 

-key KEYNAME 
-key KEYNAME -value VALUENAME

Get the key value. If -value is not specified, then the entire key contents are viewed. To view all subkeys, specify -r (for recursive). 

-set -key KEYNAME [ -type TYPE ] VALUE 
-set -key KEYNAME -value VALUENAME [ -type TYPE ] VALUE

Set the key value. If -value is not specified, the default value will be set. VALUE must be appropriate for the TYPE specified. PS_REG_STR is assumed if -type is not specified. 

-delete -key KEYNAME 
-delete -key KEYNAME -value VALUENAME

Delete the specified key or value. If -value is not specified, then the entire key and all subkeys will be deleted. 

-export -key KEYNAME [ -file FILENAME ]

Export the given key, including all values and subkeys, to standard output or the named file. 

-import [ -file FILENAME ]

Import keys and values from either the standard input or the named file.

For all options, the parameters are defined as follows: 

KEYNAME := PS_HKEY/Subkey/Path 
PS_HKEY := { PS_HKEY_CONFIG | PS_HKEY_CLASSES | PS_HKEY_USER } 
VALUENAME := value name or 'default' 
TYPE := { PS_REG_STR | PS_REG_UINT32 | PS_REG_UINT64 }

Examples of Configuring the Linux Client

This section provides some examples of configuring the Linux client using psregedit.

To display all your current settings for the Linux client in a scrollable list in the standard output: 

psregedit -key PS_HKEY_CONFIG -r | less

To specify that your client allow connections to remote servers: 

psregedit -set -key "PS_HKEY_CONFIG/Software/Pervasive Software/Microkernel Router" 
-value "Remote" yes

For more information about specific configuration settings, see Pervasive.SQL User's Guide and Configuration Reference for the Linux Client .

Configuration Notes

This section contains important concepts on configuring your Linux client properly.

Case of Setting Values

When checking or editing the values of settings, the Linux client performs a case-insensitive comparison. For example, entering 'Yes' or 'yes' for a setting value is interpreted identically by the Linux client. The names of registry keys are also handled in a case-insenstive manner by the psregedit utility.

Client Performance Affected by "Local" Setting

When the Linux client interface is first activated, it populates its default settings in the Pervasive registry. The client interface does not have knowledge on whether its installation includes a server engine or not (All Pervasive engines also contain the client components). Therefore, it sets the "Local" setting to yes. This can have an impact on the performance of your Linux client.

If the machine on which you are using the client interface does not have a server engine, you should set the Local setting to no. See Use Local MicroKernel Engine for a reference entry for this setting.

File Names with Embedded Spaces

By default, the Linux client interface does not support file names that contain embedded spaces.

For example: 

/mymount/usr/gary/file with spaces.mkd

If you want to use file names with embedded spaces, you need to change the "Embedded Spaces" setting. See Embedded Spaces for a reference of this setting.

Configuration Reference for the Linux Client

This section lists all configuration settings for the Linux client.

Btrieve Requester Settings

The Btrieve Requester settings for the Linux client can be found under the key:

Key for Btrieve Requester

Use this as the -key for changing settings of this type: 

-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Btrieve Requester/Version 8/Settings"

Values for Btrieve Requester Settings

The following settings are located under this key, which are denoted by the -value parameter:

Embedded Spaces
Name
Type
Range
Default
Units
Embedded Spaces
PS_REG_STR
yes/no
no
N/A
 
-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Btrieve Requester/Version 8/Settings" 
-value "Embedded Spaces"

This option instructs the Btrieve Interface to allow embedded spaces in filenames for Btrieve operations.

Comm Settings

The communications settings for the Linux client can be found under the key:

Key for Communication Settings

Use this as the -key for changing settings of this type. 

-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Version 8/Settings"

Values for Communication Settings

The following settings are located under this key, which are denoted by the -value parameter:

Supported Protocols
Name
Type
Range
Default
Units
Supported Protocols
PS_REG_STR
N/A
TCPIP
N/A
 
-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Version 8/Settings" 
-value "Supported Protocols"

This setting specifies the protocols that are used by the Communications Requester. For the Linux client, the only valid value for this setting is the default: TCP/IP.

Enable AutoReconnect
Name
Type
Range
Default
Units
Enable AutoReconnect
PS_REG_STR
yes/no
no
N/A
 
-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Version 8/Settings" 
-value "Enable AutoReconnect"

This setting specifies whether you want the client to attempt to auto-reconnect during a network outage. A setting of yes means Auto Reconnect is enabled.

Auto Reconnect is not in effect unless this setting is also enabled in the server configuration.

Note
The Pervasive Linux client supports this auto-reconnect feature, but currently the Linux server does not. Therefore, you can only use the AutoReconnect (PARC) feature from a Linux client connecting to Windows or NetWare servers.

Max Multiple Connections
Name
Type
Range
Default
Units
Max Multiple Connections
PS_REG_UINT32
0-256
0
N/A
 
-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Version 8/Settings" 
-value "Max Multiple Connections"

This setting controls the maximum number of connections that this client will make to a Pervasive.SQL server using the same Client ID.

When you specify 0, Pervasive.SQL uses internal defaults, which is 16 for the TCP/IP protocol.

Note
The server must be of version 8.0 or above for this setting to be used.

Log Statistics
Name
Type
Range
Default
Units
Log Statistics
PS_REG_STR
Yes/No
No
N/A
 
-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Version 8/Settings" 
-value "Log Statistics"

This setting enables communications statistics to be recorded.

MicroKernel Router Settings

The MicroKernel Router settings for the Linux client can be found under the following key:

Key for MicroKernel Router

Use this as the -key for changing settings of this type. 

-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
MicroKernel Router/Version 8/Settings"

Values for MicroKernel Router

The following settings are located under this key:

Use Local MicroKernel Engine
Name
Type
Range
Default
Units
Local
PS_REG_STR
yes/no
yes
N/A
 
-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
MicroKernel Router/Version 8/Settings" 
-value "Local"

This setting determines whether a local application tries to connect to a local engine. If set to no, no attempt is made to connect to a local engine.

Use Remote MicroKernel Engine
Name
Type
Range
Default
Units
Requester
PS_REG_STR
yes/no
yes
N/A
 
-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
MicroKernel Router/Version 8/Settings" 
-value "Requester"

This setting specifies whether the MicroKernel Router allows access to a Server or Workgroup engine running on a remote server. If this value is set to yes, and Use Local MicroKernel Engine is set to yes, the remote server is tried first.

For information about UNC paths in relation to this setting, see Target Engine and UNC Paths .

Diagnostic Configuration

These settings are only applicable if you are using the Trace requesters introduced with Pervasive.SQL V8. You should only use the trace requesters when debugging an application based on Pervasive.SQL. For more information about the tracing requesters, see What's New in Pervasive.SQL V8.

Key for Diagnostics Settings

Use this as the -key for changing settings of this type. 

-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Diagnostics"

Values for Diagnostics Key

The following settings are available under this key:

Trace Level

Controls the level of detail in the output. It is suggested you set it to "verbose" for maximum output. 

-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Diagnostics" 
-value "Trace Level"
Trace File

Set to a specific file name (for example, /usr/local/psql/trace.txt) where you want the output to appear. The file is created as needed. 

-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Diagnostics" 
-value "Trace File"
Trace Append

Always set to "yes". 

-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Diagnostics" 
-value "Trace Append"
Trace Modules

Determines which modules write debug output. Set to "all" or to the name of the specific LIBS, such as "psqlnsl" or for multiple libraries, "psqlnsl, psqlmif, psqlupi". 

-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Diagnostics" 
-value "Trace Modules"
Trace Buffer Length

Controls how many bytes of raw hex data is written to the output file when buffers are dumped. Start with the default (32 bytes) and increase if needed. 

-key "PS_HKEY_CONFIG/Software/Pervasive Software/ 
Communications Requester/Diagnostics" 
-value "Trace Buffer Length"

Target Engine and UNC Paths

The requester has two settings "Local" and "Requester".

For UNC paths to work properly from a client, the following steps must be performed:

Note
You cannot send use a UNC path that points to the local Linux machine. However, you can use a path that is in the UNC style such as
//localhost/usr/loca/psql/data/samples/sample.btr

If you do not want an engine on your file server (that is, you want to use the client's local engine), then you will need to mount the remote file system on the client, and modify the path so that it is a "native format" path and not UNC format. For example, the following path is a native Linux format: 

/mnt/myremotedata/sample.btr

Prev
Win16 Client Configuration Parameters		 Contents
Up
Check for Revisions 		Next
Settings and Features that are Not Applicable to Linux Client