The configuration language is used in remote configuration files and for interactive configuration through a TELNET connection. The configuration language provides commands for:

• Assigning and displaying parameter values
  

• Reading values from NVRAM and from files
  

• Writing values to NVRAM and to files
  

• Locking out other clients from the database
  

• Protecting parameters from modification or display
  

Table 6-2 lists the general-purpose commands you can use in remote configuration files and for interactive configuration through a TELNET connection. Table 6-3 lists commands for interactive configuration through a TELNET connection only. Bold text indicates a parameter name, square brackets ( [ ] ) indicate command options, and bold italic text indicates a variable.

Table 6-2 Configuration Commands for Files and Interactive Use

¹ This command is not available when accessing the Preferences daemon through a TELNET connection

² The protect commands are irreversible. You can remove protection only by rebooting the terminal.

Table 6-3 Configuration Commands for Interactive Use Only

Assigning Values to Configuration Parameters

Values can be set through simple assignment statements or in tables. Parameter names, permitted values, and table entry names for all read/write parameters are given in the Remote Configuration Parameter Quick Reference.

Simple Assignment Statements

A simple assignment consists of an optional set command, a parameter name followed by an equals sign (=), and a single value. For example:

boot-tcpip-desired-server = 192.43.153.16
set boot-tcpip-desired-server = 192.43.153.16

The end of a simple assignment statement is indicated by a newline or carriage return.

Tables and Rows

Parameters that can take more than one value or require a series of related values are stored in tables composed of rows. For example, each row in the exec-startup-commands table consists of a single local client name or a local client name followed by arguments:

exec-startup-commands = {
     { wm }
     { term }
     { "login eagle" }
}

When resetting values in a row, resetting an entire row, or adding and deleting rows, you can use the row number as an index into the table. This is useful mainly in configuring a terminal through a TELNET connection. For example, to add a fourth row to the exec-startup-commands table:

exec-startup-commands[4] = { lat }

To add a row to the end of a table, use the index number -1. For example:

exec-startup-commands[-1] = { lat }

If you represent the parameters in a row as simple assignment statements enclosed in parentheses, their order in the row does not matter. Using assignment statements in a row is especially useful if you are not defining all the parameters in the row. The following example shows how to reset only the baud rate in row 1 of the serial-interfaces-table, while other values in the row retain their current values.

serial-interfaces-table[1]baud-rate = 9600

In contrast, the following assignment defines the baud rate and resets the other parameters in the row to their default values:

serial-interfaces-table[1] = {(baud-rate = 9600)}

Specify an empty table or empty row in a table as follows:

• Empty row in a table: table[row number] = { }
  

• Empty table: table = { } or table = {{ }}
  

For example:

config-access-control-list = { }
config-access-control-list[2] = { }

The following list describes the types of values used in remote configuration parameters.

• Strings-The keywords null or nil indicate that the parameter has no value. String values that contain embedded white space must be surrounded by double or single quotation marks (" or `).
  

• Integers-To specify integer values, use decimal or hexadecimal notation.
  

• The keyword "default"-All parameters accept the keyword default, which assigns the default value to the parameter. For example, the following assignments have the same effect:
  

  
  boot-automatically = default
  boot-automatically = true
  

• Boolean values-For parameters that have Boolean values, you can use the value pairs "yes/no," "on/off," or "true/false." For example, the following assignments are equivalent:
  

  
  boot-automatically = on
  boot-automatically = true
  boot-automatically = yes
  

• Choices-Many parameters take specific choices. For example, the exec-startup-commands parameter takes the command names of local clients, such as term and login.
  

• Filenames-For parameters that take filenames as arguments, you can always specify filenames as absolute pathnames in the form /a/b/c.
  
  Parameters for which there is a default directory accept relative pathnames as well.
  

Syntax rules for setting remote configuration parameter values are described in the following list:

• Case-Uppercase and lowercase characters are not distinguished in parameter names, choices, or Boolean values. You may enter them in the form you find most readable. For example, the following assignments are identical functionally:
  

  
  boot-automatically = true
  Boot-automatically = True
  BOOT-AUTOMATICALLY = TRUE
  

  
  When values are not part of the configuration language, however, case is preserved. For example:
  

  • In the xserver-initial-x-resources parameter, you can set client resources. Values must follow the same form as the resource settings in a resources file, such as .Xdefaults.

  • Filenames are interpreted exactly you enter them.

  • Quoted strings are interpreted as you enter them.

• End-of-line-If a statement extends past the end of line, you can use a backslash (\) to prevent interpretation of the newline. This is not necessary for tables, in which curly braces ({ }) function as delimiters.
  

• White space-White space (the separator between grammatical elements) may be spaces, tabs, newline characters, or carriage returns. White space is not required before or after the equals sign in an assignment statement. For example, the following three assignments are functionally identical:
  

  
  boot-automatically=true
  boot-automatically       =        true
  boot-automatically \
  = \
  true
  

  
  As the last example shows, an assignment statement may span several lines.
  

• Special characters-You can use the C-language convention of a backslash (\) for escaping special characters.
  

You can include a comment in a remote configuration file by typing a pound sign (#) at the beginning of each line of comments. For example, to explain why a parameter was set to a specific value, you might type:

#Set to local to ensure that terminal
#boots from PCMCIA card instead of network host
boot-desired-source = local

Comments can also be appended to a line. For example:

boot-desired-source = local       #Boot from PCMCIA




Note:
Do not append comments to a line in statements that extend for 
more than one line.

A parameter can be assigned any number of times. Each assignment is processed as it is read, overriding the previous assignment.

The only exception to this rule is the unit-license-key parameter, which must be assigned for each license key when using node licensing. For more information about licensing, see the System Administrator's Guide.

Listing Commands in Order

Assignment commands are interpreted in the order in which they appear. This affects assignments that depend upon the prior execution of other statements and parameters assigned more than once.

Although most parameters do not depend on other parameters being set previously, there are a few exceptions. For example, when using a name service you may specify hosts by their names instead of their addresses. Before you can refer to a host by its name in the remote configuration file, you must set the name service parameters. For example:

#Set the name service parameters
tcpip-name-server-protocol = dns
tcpip-name-servers = { 192.43.153.16  192.43.153.24 }
apply
#Set a parameter to a host name
boot-tcpip-desired-server = peregrine




Note:
The parameters that specify the name service must be followed 
by an apply command. 

If a parameter is assigned more than once in a configuration file, the last assignment supersedes all previous assignments.

Saving Parameters in NVRAM

When the X server reads a configuration file, it automatically saves settings to NVRAM when it reaches the end of the file.

When using interactive configuration via TELNET, you must enter an apply command to save parameters in NVRAM.

The config-auto-save-nvram parameter determines whether parameters are saved automatically to NVRAM (Change Setup Parameters -> Configuration [Configuration Daemon section] -> Auto Save NVRAM) . For more information about auto-save, see " Configuring the Apply Command" on page 6-34.