172 lines
17 KiB
HTML
172 lines
17 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
|
||
|
|
<html>
|
||
|
|
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
|
||
|
|
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||
|
|
<title>Configuration File Definition (Advanced)</title>
|
||
|
|
<link href="scripts/style.css" type="text/css" rel="stylesheet">
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body>
|
||
|
|
<h3>Configuration File Definition (Advanced)</h3>
|
||
|
|
<p>A typical NTP monitoring packet</p>
|
||
|
|
<p>Last update: <csobj format="ShortTime" h="25" locale="00000409" region="0" t="DateTime" w="61">19:46</csobj> UTC <csobj format="LongDate" h="25" locale="00000409" region="0" t="DateTime" w="223">Friday, June 16, 2006</csobj></p>
|
||
|
|
<br clear="left">
|
||
|
|
<hr>
|
||
|
|
<h4>Table of Contents</h4>
|
||
|
|
<ul>
|
||
|
|
<li class="inline"><a href="#synopsis">Synopsis</a><br>
|
||
|
|
<li class="inline"><a href="#files">Files</a>
|
||
|
|
<li class="inline"><a href="#high-level">High-Level Description</a>
|
||
|
|
<li class="inline"><a href="#detailed">Detailed Description</a>
|
||
|
|
<li class="inline"><a href="#guidelines">Guidelines for Adding Configuration Commands </a>
|
||
|
|
</ul>
|
||
|
|
<h4 id="synopsis">Synopsis</h4>
|
||
|
|
<p>The NTP configuration process is driven by a phrase-structure grammar which is used to specify the format of the configuration commands and the actions needed to build an abstract syntax tree (AST). The grammar is fed to a parser generator (Bison) which produces a parser for the configuration file.</p>
|
||
|
|
<p>The generated parser is used to parse an NTP configuration file and check it for syntax and semantic errors. The result of the parse is an AST, which contains a representation of the various commands and options. This AST is then traversed to set up the NTP daemon to the correct configuration.</p>
|
||
|
|
<p>This document is intended for developers who wish to modify the configuration code and/or add configuration commands and options. It contains a description of the files used in the configuration process as well as guidelines on how to construct them.</p>
|
||
|
|
<h4 id="files">Files</h4>
|
||
|
|
<p>A brief description of the files used by the configuration code is given below:</p>
|
||
|
|
<table border="1">
|
||
|
|
<tbody>
|
||
|
|
<tr>
|
||
|
|
<th width="179">File</th>
|
||
|
|
<th width="537">Description</th>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td valign="top"><b>ntp_config.y</b></td>
|
||
|
|
<td>This file is a Bison source file that contains the phrase-structure grammar and the actions that need to be performed to generate an AST.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td valign="top"><b>ntp_config.c</b></td>
|
||
|
|
<td>This file contains the major chunk of the configuration code. It contains all the functions that are called for building the AST as well as the functions that are needed for traversing the AST.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td valign="top"><b>ntp_config.h</b></td>
|
||
|
|
<td>This file is the header file for <b>ntp_config.c</b>. It mainly contains the structure definitions needed to build the AST. </td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td valign="top"><b>ntp_scanner.c</b></td>
|
||
|
|
<td>This file contains the code for a simple lexical analyzer. This file is directly included into the <b>ntp_config.c</b> file since this code is only used by the configuration code. The most important function in this file is <tt>yylex</tt>, which is called by the generated parser to get the next token on the input line.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td valign="top"><b>ntp_data_structures.c</b></td>
|
||
|
|
<td>This file contains a generic implementation of a priority queue and a simple queue. This code can be used to create a queue for any structure.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td valign="top"><b>ntp_data_structures.h</b></td>
|
||
|
|
<td>This header file contains the structure declarations and function prototypes needed to use the data structures defined in <b>ntp_data_structures.c</b>. This file forms the public interface of the data structures.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td valign="top"><b>ntp_config.tab.c</b></td>
|
||
|
|
<td>This file is generated by Bison from the <b>ntp_config.y</b> file. This file is also included directly into the configuration code.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
<h4 id="high-level">High-Level Description</h4>
|
||
|
|
<p>A high-level description of the configuration process showing where all the files fit in is given below:</p>
|
||
|
|
<p>The scanner reads in an NTP configuration file and converts it into tokens. The Bison generated parser reads these tokens and converts them into an AST. The AST traverser consists of a set of functions that configure parts of NTP on the basis of what is on the tree. A more detailed description of these parts and the files used is given below:</p>
|
||
|
|
<h4 id="detailed">Detailed Description</h4>
|
||
|
|
<dl>
|
||
|
|
<dt><b>ntp_scanner.c</b>
|
||
|
|
<dd>This file contains the scanner. The scanner is a small program that converts an input NTP configuration file into a set of <b>tokens</b> that correspond to <b>lexemes</b> in the input. Lexemes are strings in the input, delimited by whitespace and/or special characters. Tokens are basically unique integers that represent these lexemes. A different token is generated for each reserved word and special character in the input. There are two main functions in the public interface of this file:
|
||
|
|
<dt><tt>int yylex</tt>()
|
||
|
|
<dd>This function is called <tt>yylex</tt> for historical reasons; <tt>lex</tt> is a program that takes a set of regular expressions and generates a scanner that returns tokens corresponding to those regular expressions. The name of the generated function is called <tt>yylex</tt>. We aren't using<b> </b><tt>lex</tt><b> </b>because it requires linking against an external library and we didn't want to increase the compile-time requirements of NTP.
|
||
|
|
<dd>History lessons aside, this function basically checks to see if the next input character is a special character as defined in the array <tt>char special_char[]</tt>. (The function <tt>int is_special(char ch)</tt>, can be used for this.) If yes, the special character is returned as the token. If not, a set of characters is read until the next whitespace or special character is encountered. This set of characters forms the lexeme; <tt>yylex</tt> then checks whether this lexeme is an integer, a double, an IP address or a reserved word. If yes, the corresponding token is returned. If not, a token for a string is returned as the default token.
|
||
|
|
<dt><tt>struct state *create_keyword_scanner(struct key_tok *<i>keyword_list</i>)</tt>
|
||
|
|
<dd>This function takes a list of (<i>keyword, token</i>) pairs and converts them into a trie that can recognize the keywords (reserved words). Every time the scanner reads a lexeme, it compares it against the list of reserved words. If it finds a match, it returns the corresponding token for that keyword.
|
||
|
|
<dt><b>ntp_data_structures.c</b>
|
||
|
|
<dd>This file contains an implementation of a generic priority queue and FIFO queue. By generic, we mean that these queues can hold element of any type (integers, user-defined structs, etc.), provided that these elements are allocated on the heap using the function <tt>void</tt> *<tt>get_node(size_t size)</tt>. Note that the prototype for this function is exactly the same as that of <tt>malloc</tt> and that it can be used in the exact same way. Behind the scenes, <tt>get_node</tt> calls <tt>malloc</tt> to allocate <i>size</i> plus some extra memory needed for bookkeeping. The allocated memory can be freed using the function <tt>void free_node (void *<i>my_node</i>)</tt>. In addition to these two functions, the public interface of this file contains the following functions:
|
||
|
|
<dt><tt>queue *create_priority_queue(int (*get_order)(void *, void*))</tt>
|
||
|
|
<dd>This function creates a priority queue in which the order of the elements is determined by the <tt>get_order</tt><b> </b>function that is passed as input to the priority queue. The <tt>get_order</tt><b> </b>function should return positive if the priority of the first element is less than the priority of the second element.
|
||
|
|
<dt><tt>queue *create_queue(void)</tt>
|
||
|
|
<dd>This function creates a FIFO queue. It basically calls the <tt>create_priority_queue</tt> function with the <tt>get_fifo_order</tt><b> </b>function as its argument.
|
||
|
|
<dt><tt>void destroy_queue(queue *<i>my_queue</i>)</tt>
|
||
|
|
<dd>This function deletes <tt><i>my_queue</i></tt><b> </b>and frees up all the memory allocated to it an its elements.
|
||
|
|
<dt><tt>int empty(queue *</tt><i><tt>my_queue</tt></i><tt>)</tt>
|
||
|
|
<dd>This function checks to see if <i><tt>my_queue</tt></i> is empty. Returns <tt>true</tt> if <tt><i>my_queue</i></tt> does not have any elements, else it returns false.
|
||
|
|
<dt><tt>queue *enqueue(queue *<i>my_queue</i>, void *<i>my_node</i>)</tt>
|
||
|
|
<dd>This function adds an element, <i><tt>my_node</tt></i>, to a queue, <i><tt>my_queue</tt></i>. <i><tt>my_node</tt></i> must be allocated on the heap using the <tt>get_node</tt> function instead of <tt>malloc</tt>.
|
||
|
|
<dt><tt>void *dequeue(queue *<i>my_queue</i>)</tt>
|
||
|
|
<dd>This function returns the element at the front of the queue. This element will be element with the highest priority.
|
||
|
|
<dt><tt>int get_no_of_elements(queue *<i>my_queue</i>)</tt>
|
||
|
|
<dd>This function returns the number of elements in <tt><i>my_queue</i></tt>.
|
||
|
|
<dt><tt>void append_queue(queue *<i>q</i>1, queue *<i>q</i>2)</tt>
|
||
|
|
<dd>This function adds all the elements of <tt><i>q</i>2</tt> to <tt><i>q</i>1</tt>. The queue <tt><i>q</i>2</tt> is destroyed in the process.
|
||
|
|
<dt><b>ntp_config.y</b>
|
||
|
|
<dd>This file is structured as a standard Bison file and consists of three main parts, separated by <tt>%%</tt>:
|
||
|
|
</dl>
|
||
|
|
<ol>
|
||
|
|
<li>The prologue and bison declarations: This section contains a list of the terminal symbols, the non-terminal symbols and the types of these symbols.<li>The rules section: This section contains a description of the actual phrase-structure rules that are used to parse the configuration commands. Each rule consists of a left-hand side (LHS), a right-hand side (RHS) and an optional action. As is standard with phrase-structure grammars, the LHS consists of a single non-terminal symbol. The RHS can contain both terminal and non-terminal symbols, while the optional action can consist of any arbitrary C code.
|
||
|
|
<li>The epilogue: This section is left empty on purpose. It is traditionally used to code the support functions needed to build the ASTs Since, we have moved all the support functions to <b>ntp_config.c</b>, this section is left empty.
|
||
|
|
</ol>
|
||
|
|
<h4>Prologue and Bison Declarations</h4>
|
||
|
|
<p>All the terminal symbols (also known as tokens) have to be declared in the prologue section. Note that terminals and non-terminals may have values associated with them and these values have types. (More on this later). An unnamed union has to be declared with all the possible types at the start of the prologue section. For example, we declare the following union at the start of the <b>ntp_config.y</b> file:</p>
|
||
|
|
<p class="style1"><tt>%union {<br>
|
||
|
|
char *String;<br>
|
||
|
|
double Double;<br>
|
||
|
|
int Integer;<br>
|
||
|
|
void *VoidPtr;<br>
|
||
|
|
queue *Queue;<br>
|
||
|
|
struct attr_val *Attr_val;<br>
|
||
|
|
struct address_node *Address_node;<br>
|
||
|
|
struct setvar_node *Set_var;<br>
|
||
|
|
/* Simulation types */<br>
|
||
|
|
server_info *Sim_server;<br>
|
||
|
|
script_info *Sim_script;<br>
|
||
|
|
}</tt></p>
|
||
|
|
<p>Some tokens may not have any types. For example, tokens that correspond to reserved words do not usually have types as they simply indicate that a reserved word has been read in the input file. Such tokens have to be declared as follows:</p>
|
||
|
|
<p><tt>%token T_Discard<br>
|
||
|
|
%token T_Dispersion</tt></p>
|
||
|
|
<p>Other tokens do have types. For example, a <tt>T_Double</tt> token is returned by the scanner whenever it sees a floating-point double in the configuration file. The value associated with the token is the actual number that was read in the configuration file and its type (after conversion) is double. Hence, the token <tt>T_Double</tt> will have to be declared as follows in the prologue of <b>ntp_config.y</b> file:</p>
|
||
|
|
<p><tt>%token <Double> T_Double </tt></p>
|
||
|
|
<p>Note that the declaration given in the angled brackets is not <tt>double</tt> but <tt>Double</tt>, which is the name of the variable given in the <tt>%union {}</tt> declaration above.</p>
|
||
|
|
<p>Finally, non-terminal symbols may also have values associated with them, which have types. This is because Bison allows non-terminal symbols to have actions associated with them. Actions may be thought of as small functions which get executed whenever the RHS of a non-terminal is detected. The return values of these functions are the values associated with the non-terminals. The types of the non-terminals are specified with a <tt>%type</tt> declaration as shown below:</p>
|
||
|
|
<p><tt>%type <Queue> address_list<br>
|
||
|
|
%type <Integer> boolean</tt></p>
|
||
|
|
<p>The <tt>%type</tt> declaration may be omitted for non-terminals that do not return any value and do not have type information associated with them.</p>
|
||
|
|
<h4>The Rules Section </h4>
|
||
|
|
<p>The rule section only consists of phrase-structure grammar rules. Each rule typically has the following format:</p>
|
||
|
|
<p><tt>LHS : RHS [{ Actions }]<br>
|
||
|
|
;</tt></p>
|
||
|
|
<p>where LHS consists of a single non-terminal symbol and the RHS consists of one or more terminal and non-terminal symbols. The <tt>Actions</tt> are optional and may consist of any number of arbitrary C statements. Note that Bison can only process LALR(1) grammars, which imposes additional restrictions on the kind of rules that can be specified. Examples of rules are shown below:</p>
|
||
|
|
<p><tt>orphan_mode_command<br>
|
||
|
|
: T_Tos tos_option_list<br>
|
||
|
|
{ append_queue(my_config.orphan_cmds, $2); }<br>
|
||
|
|
;</tt></p>
|
||
|
|
<p><tt>tos_option_list<br>
|
||
|
|
: tos_option_list tos_option { $$ = enqueue($1, $2); }<br>
|
||
|
|
| tos_option { $$ = enqueue_in_new_queue($1); }<br>
|
||
|
|
;</tt></p>
|
||
|
|
<p>The <tt>$n</tt> notation, where <tt>n</tt> is an integer, is used to refer to the value of a terminal or non-terminal symbol. All terminals and non-terminal symbols within a particular rule are numbered (starting from 1) according to the order in which they appear within the RHS of a rule. <tt>$$</tt> is used to refer to the value of the LHS terminal symbol - it is used to return a value for the non-terminal symbol specified in the LHS of the rule.</p>
|
||
|
|
<h4>Invoking Bison </h4>
|
||
|
|
<p>Bison needs to be invoked in order to convert the <b>ntp_config.y</b> file into a C source file. To invoke Bison, simply enter the command:</p>
|
||
|
|
<p><tt>bison ntp_config.y</tt></p>
|
||
|
|
<p>at the command prompt. If no errors are detected, an <b>ntp_config.tab.c</b> file will be generated by default. This generated file can be directly included into the <b>ntp_config.c</b> file.</p>
|
||
|
|
<p>If Bison report shift-reduce errors or reduce-reduce errors, it means that the grammar specified using the rules in not LALR(1). To debug such a grammar, invoke Bison with a <tt>-v</tt> switch, as shown below. This will generate a <b>ntp_config.output</b> file, which will contain a description of the generated state machine, together with a list of states that have shift-reduce/reduce-reduce conflicts. You can then change the rules to remove such conflicts.</p>
|
||
|
|
<p><tt>bison -v ntp_config.y</tt></p>
|
||
|
|
<p>For more information, refer to the <a href="http://www.gnu.org/software/bison/manual/html_mono/bison.html">Bison manual</a>.</p>
|
||
|
|
<p><b>ntp_config.c</b></p>
|
||
|
|
<p>This file contains the major chunk of the configuration code including all the support functions needed for building and traversing the ASTs. As such, most of the functions in this file can be divided into two groups:</p>
|
||
|
|
<ol>
|
||
|
|
<li>Functions that have a <tt>create_</tt> prefix. These functions are used to build a node of the AST.
|
||
|
|
<li>Functions that have a <tt>config_</tt> prefix. These functions are used to traverse the AST and configure NTP according to the nodes present on the tree.
|
||
|
|
</ol>
|
||
|
|
<h4>Guidelines for Adding Configuration Commands</h4>
|
||
|
|
<p>The following steps may be used to add a new configuration command to the NTP reference implementation:</p>
|
||
|
|
<ol>
|
||
|
|
<li>Write phrase-structure grammar rules for the syntax of the new command. Add these rules to the rules section of the <b>ntp_config.y</b> file.
|
||
|
|
<li>Write the action to be performed on recognizing the rules. These actions will be used to build the AST.
|
||
|
|
<li>If new reserved words are needed, add these to the <tt>struct key_tok keyword_list[]</tt>structure in the <b>ntp_config.c </b>file. This will allow the scanner to recognize these reserved words and generate the desired tokens on recognizing them.
|
||
|
|
<li>Specify the types of all the terminals and non-terminal symbols in the prologue section of the <b>ntp_config.c</b> file.
|
||
|
|
<li>Write a function with a <tt>config_</tt> prefix that will be executed for this new command. Make sure this function is called in the <tt>config_ntpd()</tt>function.
|
||
|
|
</ol>
|
||
|
|
<hr>
|
||
|
|
<address><a href="mailto:skamboj@udel.edu">Sachin Kamboj</a></address>
|
||
|
|
<script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
|
||
|
|
</body>
|
||
|
|
|
||
|
|
</html>
|