To add an access record, start the access file manager and select option [1] from the main menu. The manager will then present a series of five prompts, one for each field in the record. The first field is the Client Machine Name field. The prompt will look something like this:
A value of "*" for client machine name means that this record will match all clients for which there are no other records. You cannot use alias names. The name must be the official machine name. Enter the official machine name [*]:
Enter a client machine name or accept the default value.
The second prompt is for the Client Username. If this field is blank, any user name will match. For Windows and DOS clients that do not define a USERNAME or USER environment variable, this field should be left blank or set to "USER" (see Section 8.2 Access Records).
If no client user name is entered it implies any user. Enter client user name []:
Enter a client user name or accept the default value.
The third prompt fills in the Local Username field. The Local Username is the name that AcuServer will use when executing access requests for requesters that match the first two fields of this record. Note that if the Local Username is not a valid name on the server, the server will attempt to use the value of the server configuration variable DEFAULT-USER (if defined). If DEFAULT-USER is not defined, the connection will be refused (AcuServer returns an error 9D,103).
A value of 'same as client' for local user name means to use the client user name. If no local user name is entered DEFAULT-USER is used. Enter the local user name [same as client]:
Enter a local user name or accept the default value.
The fourth prompt allows you to specify a password which must be supplied by requesters who match this record. The inclusion of a password is optional.
The password can be up to eight characters long. The set of allowable characters includes: upper and lower case letters, numbers, the space character and most special characters (all ASCII characters numbered 32-126). Delete, escape and other non-printable characters are not allowed.
The password characters are not echoed on the screen when entered. You will be asked to enter the password a second time to verify that it was entered correctly.
If no password is entered it implies none. Enter password []: Retype password for verification:
Should the password verification fail, you will see the following message:
Mismatch - try again. If no password is entered it implies none. Enter password []:
The final prompt allows you to specify a umask. The umask is a three-digit code that sets the read and write permissions on new files created for the requester by AcuServer. For more about umask see the end of Section 4.3 Ownerships and Permissions , and your UNIX operating system documentation.
The umask defines the file creation mask for all files created by this user. It must be an octal value between 000 and 777. Enter umask [002]:
Enter a umask value or accept the default value. If an invalid umask value is entered, you will see this message:
Invalid value for umask - try again.
After you specify a valid umask, the access file manager adds the record to the server access file.
Record added. Press <Return> to continue...
If you accept all of the defaults when creating the record, the entry will look like:
Client Machine Name Client Username Local Username Password Umask * <same as client> <none> 002
This record entry will match any client and allow any user to connect to the server, provided that:
Note that record entries which "match all" ("*") client machines but specify a Client Username, will never be matched and should not be created. For example:
Client Machine Name Client Username Local Username Password Umask * bernie <same as client> <none> 002
This is a restriction in the current implementation of the verification algorithm. The restriction will most likely be removed in a later release of AcuServer. For a complete description of the AcuServer verification logic, see Section 8.4 AcuServer Connection Logic .
Through inclusion or exclusion of wild cards, named entries, passwords and umasks, it is possible to construct a server access file that allows open, unrestricted access, rigid, tightly controlled access, or most any level in between.