 | Advanced Operations Guide (v9 SP2 (9.5) revision 1) |  |
|
You can configure both Pervasive PSQL Clients and Servers using the graphical utility Pervasive PSQL Control Center or the command-line interface utility bcfg. For PCC, see Using Pervasive PSQL Control Center in Pervasive PSQL User's Guide. For bcfg, see Configuration Through CLI Utility .
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.
When the Linux client interface is first activated, it populates its default settings in the Pervasive registry. The Pervasive PSQL Client does not have knowledge on whether its installation includes a server engine or not. 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 does not have a server engine, you should set the Local setting to no. See Use Local MicroKernel Engine .
By default, the Linux client interface does supports file names that contain embedded spaces.
For example:
If you want to use file names without embedded spaces, you need to change the "Embedded Spaces" setting. See Embedded Spaces .
The following table lists the configuration options for the Linux client.
Access contains the following configuration settings:
See Use Local MicroKernel Engine .
See Use Remote MicroKernel Engine .
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/local/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:
See Use IDS .
See Wire Encryption .
See Wire Encryption Level .
Communication protocols contains the following configuration settings:
This setting specifies the protocols on which the database engine listens for client connections. If more than one protocol is specified, the database engine listens on all specified protocols. TCP/IP is the only supported protocol to a Pervasive PSQL Server running on a Linux platform. The available options are:
This setting specifies whether you want the client to attempt to auto-reconnect during a network outage. A setting of on means Auto Reconnect is enabled.
Auto Reconnect is not in effect unless this setting is also enabled in the server configuration.
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.
Application characteristics contains the following configuration settings:
See Embedded Spaces .
See Verify Key Length .
|
Chapter contents
Prev topic: Win32 Client Configuration Parameters
|