When you usencdinstall to add terminals, the following files are created:
❏ Two terminal-specific files:
— The name of the terminal-specific file controlled by the system administrator is the terminal’sIPaddress converted to hexadecimal format. For example, the terminal withIP address 192.40.150.4 has a
configuration file namedC0289604.
— The name of the file for the user’s configuration data is the same as the terminal-specific file plus the suffix .stp; for example,C0289604.stp.
❏ The generic filencd_std (created only once, not created if it already exists). This file is for storing configuration data common to a group of terminals.
All configuration files are placed byncdinstallin the default configuration file directory (/usr/lib/X11/ncd/configs) on the boot host. On hosts using secureTFTP, configuration files are normally in/tftpboot/usr/lib/X11/ncd/configs. If the file access method isTFTP, the configuration files must be world-writable and world-readable.
If you do not usencdinstall to add terminals or you prefer to create your own configuration files, you can start with the example file on theNCDwareCD-ROM.
The Terminal-Specific Configuration Files
This section describes the two terminal-specific files created byncdinstall for each terminal you add.
System Administrator’s File
The terminal-specific system administrator’s configuration file created byncdinstall contains the assignments andread commands shown in the example in Figure 4-1. These entries are explained in the text following the figure.
The commands and assignments in the terminal-specific file are:
❏ The firstread statement reads the contents of the generic file and adds the assignments in the generic file to the terminal’s configuration data.
❏ The three parameters in thefile group are not always present in the file. Their purpose is to export the local file Figure 4-1 Terminal-Specific Remote Configuration File
# ncd_std -- standard terminal configuration file.
read /usr/lib/X11/ncd/configs/ncd_std
#modules-directory = "/tftpboot/modsxpt"
#modules-load-policy = {}
file-enable-nfs-server = true
file-enable-floppy-filesystem = true file-nfs-access-control-list = { { /local 0.0.0.0 Read-Only } { /xfloppy 0.0.0.0 Read-Write } }
unit-license-key = 1234567890123456 login-ncddm-enabled = true
# 01020309.stp -- auto-save file which is under user control read /usr/lib/X11/ncd/configs/01020309.stp
Lines preceded by a pound sign are comments.
❏ Theunit-license-key parameter is not always present in the file. It is placed in the file if the terminal is licensed for optional features and you enter one or more license keys while adding the terminal.
❏ Thelogin-ncddm-enabledparameter facilitates use of Java and theNCD Mosaic Browser. For more information aboutncddm, see Chapter 5 and Chapter 15.
❏ The secondread statement reads the contents of the user’s configuration file and applies settings in the file to the terminal’s configuration.
User’s File
The user’s configuration file is initially empty. Users who have access to the Setup menus in the Console can save terminal configuration information in their .stp files.
To save current changes into the.stp file:
1. From the File menu of a Setup menu (Change Quick Setup, Change Setup Parameters, or Change User Preferences), selectSave to File.
2. The name of the.stpfile is displayed in the dialog box.
Click onOK.
3. Changes are saved to the.stpfile.
You can delete the.stp files if you don’t permit users to configure their own terminals.
The Generic Remote Configuration File
Thencd_stdgeneric file contains parameters used by all terminals on the network. The terminal does not directly load the generic file if there is a specific file. The terminal-specific file reads the generic file. Figure 4-2 shows an example of the file created byncdinstall.
# ncd_std -- standard terminal configuration file tcpip-name-server-protocol = both
tcpip-dns-default-domain = ncd.com tcpip-name-servers = {
{ 139.40.202.19 } }
exec-startup-commands = { { “login 139.40.202.19” } }
xserver-default-font-path = { { “built-ins” }
{ “/usr/lib/X11/ncd/fonts/pcf/misc/” } { “/usr/lib/X11/ncd/fonts/pcf/75dpi/” } { “/usr/lib/X11/ncd/fonts/pcf/100dpi/” } { “/usr/lib/X11/ncd/fonts/pcf/dw75dpi/” } { “/usr/lib/X11/ncd/fonts/pcf/dw100dpi/” } { “/usr/lib/X11/ncd/fonts/pcf/java/” } { “/usr/lib/X11/ncd/fonts/pcf/Xol/” } }
#browser-environment = {
# { “HOME” “/usr/lib/X11/ncd/users” }
# { “BROWSER_HOME” “$HOME” }
#}
# Browser entries in file-service-table[]
file-service-table[-1] = { /tmp nil 139.40.202.19 tftp /usr/lib/X11/ncd/users/tmp }
file-service-table[-1] = { /usr/lib/X11/ncd/users nil 139.40.202.19 tftp
/usr/lib/X11/ncd/users } apply
Tip
The name service parameters must be listed first. Until the terminal has read the name service parameters, all hosts must be referenced by their IP addresses, instead of their
hostnames.
The parameters in thencd_stdfile are:
❏ Thetcpip-name-server-protocolparameter sets the name service protocol to bothDNS andIEN-116. The name service resolves hostnames and theirIP addresses.
❏ Thetcpip-dns-default-domain parameter sets the default domain suffix that is appended to hostnames in name service searches; for example, ncd.com.
❏ Each row in thetcpip-name-serversparameter table contains theIP address of a name server host. These are hosts that provide the name service protocol. By default, the boot host is the name server host.
❏ Each row in theexec-startup-commandstable contains a command for displaying a local client. The default command in the file displays a login prompt for the boot host. Because there are white spaces in the command line, the line must be surrounded by quotes.
❏ Each row in thexserver-default-font-pathtable is the pathname of a font directory containing fonts used by clients running on the terminal.
❏ The additions to thefile-service-table parameter permit users to write their preference files and hot list files from theNCD Mosaic Browser when you are usingTFTP for file access.
❏ Theapply command applies all of the preceding parameter settings to the current configuration.
Example Configuration File from the NCDware Distribution
If you don’t usencdinstallto add terminals and want to create your own configuration files, you can use the example file (hex_ip.sample) included on theNCDware distribution and installed byncdinstall in/usr/lib/X11/ncd/configs. The
parameters in the file are the same as those in Setup⇒Change Quick Setup. All parameters in the example file are set to their default values.
To use the example file:
1. Copy the file to the terminal-specific filename, which is the terminal’sIP address in hexadecimal, or to the generic filename,ncd_std.
To convert anIP address to a hexadecimal filename, you can use theUNIX bc(1) utility. For example:
% bc obase=16 192;40;154;4 C0
28 9A 4
Each portion of theIP address must be represented by two characters, so the filename should beC0289A04. 2. Edit parameters as required.
3. Make sure the file has the correct permissions. The file should be readable by all.
Editing Remote Configuration Files
You can edit any remote configuration file with a text editor (such asvi).
When editing a configuration file, be sure to retain the correct file permissions. Remote configuration files must be readable and writable by all.