Configuration
Generally, the default configuration settings for Pervasive PSQL Server and Client are sufficient. You typically do not have to configure any settings for the database engine and clients to communication and function together correctly. This subsection discusses two settings that you may want or need to configure:
•
Configuration File
•
Authentication
If you want to explore all of the configuration settings, see the chapter Configuration Reference in Advanced Operations Guide:
Configuration File
The Server configuration setting “Configuration File” defines the path to the Samba configuration file (smb.conf), which is parsed on engine startup to determine mapping between share names and server directory locations. See Configuration File (Linux engines only) in Advanced Operations Guide.
Authentication
This option specifies which type of authentication to use for access to the server engine. The available options are:
•
Emulate Workgroup Engine. Use this value when Samba is used to authenticate user access on the system.
•
Proprietary Authentication (using btpasswd). Use this value when not using Samba and the user does not have an account on the server. This allows a separate password file to be maintained when connecting to the Linux system.
•
If you are using BTPASSWD or PAM authentication on your Linux server, user names and passwords must be set up using the pvnetpass utility from clients connecting to this server. See pvnetpass in the Pervasive PSQL User's Guide.
•
Standard Linux Authentication. Use this value when not using Samba but users have accounts on the Linux system.
Supported Path Formats for Samba
From a Pervasive PSQL Client on a Windows platform, the order of path parsing is as follows:
•
\\server\share\relative\path
share denotes a valid Samba share, made accessible to a Windows client.
server reads smb.conf to determine the absolute path to the shared directory, then combines it with the relative path to get a full UNIX path. The location of smb.conf is essential for valid resolution of the file path supplied in this format on the client. If the relative path is not correct, status 12 is returned.
•
Drive:\path
drive must be a Samba drive mapped on the client. It is the client responsibility to convert it into the latter format and pass to a server, which never knows a drive mapping on the client.
*Note: Client users must be advised that share names on a Linux server are case sensitive. When mapping drives to a Linux server they must pay careful attention to the case of the share name if they want all their utilities to work properly.
•
If neither smb.conf nor the share name are found, the path defaults to \\server\absolute\path format. If the absolute path is not correct, status 12 is returned.