Configuration
Generally, the default configuration settings for 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:
•
Samba Configuration File
•
Authentication
If you want to explore all of the configuration settings, see the chapter Configuration Reference in Advanced Operations Guide:
Samba Configuration File
PSQL Server 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 and OS X 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 or OS X system.
•
If you are using BTPASSWD or PAM authentication on your Linux or OS X server, user names and passwords must be set up using the pvnetpass utility from clients connecting to this server. See pvnetpass in the PSQL User's Guide.
•
Standard Linux Authentication. Use this value when Samba is not used, but users have accounts on the Linux or OS X system.
Supported Path Formats for Samba
Windows Client
From a PSQL client on a Windows, 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 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 Windows client, from which the PSQL client determines the server where the Btrieve file resides.
Linux or OS X Client
From a PSQL client on a Linux or OS X, the order of path parsing is as follows:
•
//server/share/relative/path
Share denotes a valid Samba share name on the server.
On systems that use a third-party Samba package, server reads smb.conf to determine the absolute path to the shared directory, then combines it with the relative path to get a full path. The location of smb.conf is essential for valid resolution of the file path supplied in this format on the client.
On OS X systems that use native SMB file sharing instead of smb.conf, server resolves sharing information directly from the operating system.
In all cases, if the relative path is not correct, an error status is returned.
•
/Mount/path
Mount must be a Samba drive mounted on the Linux or OS X client, from which the PSQL client determines the server where the Btrieve file resides.
*Note: Share names for clients for a Linux server are case-sensitive. If the share name on the server and the client do not match exactly, they cannot communicate.
On Linux and OS X servers, if the PSQL engine cannot find either smb.conf or a share name, it assumes a default of \\server\absolute\path format. If the absolute path is not correct, status 12 is returned.