Lines Matching refs:inittab

47 The inittab API is designed to reduce the confusion, both for the
56 The inittab file contains information regarding the syntax and (to
62 The inittab file consists of inittab records, each being one line long
119 Comments in the inittab file begin with `#', and end with a newline.
123 The inittab file becomes the authoritative source for all DHCP options 
128       inittab file do not generally affect their inner workings.
130    o  A program can specify which entries it wants from the inittab.
137    o  In general, changing provided information in a released inittab
141    o  The inittab C API also provides functions which allow programs
142       to verify that a given entry in the inittab file is correct
146       of having an inittab.
148    o  Where a symbol is defined both in the inittab and in dhcptab(4),
149       inittab is authoritative.  EXTEND symbol definitions in
155 Each inittab entry describes a specific DHCP option and is defined as
158 In general, it is expected that inittab entries are acquired via
161 to convert the inittab entries into a different format, then the
162 fields inside the inittab entry may be read directly.  Some inittab
166 To get an inittab entry, one of the following API's must be used:
203 Some inittab consumers may need to make sure that a given inittab
204 entry has not been corrupted in the inittab file.  For those cases,
206 internal table compiled into the inittab API:
217 value of the option known internally to the inittab API.  Entries are
283 In order to aid in debugging inittab-related problems, two environment
285 before starting a program which uses the inittab API.
288 inittab API will print useful diagnostic messages handy in tracking
289 down problems in the inittab file.  If DHCP_INITTAB_PATH is an
291 of the inittab file, instead of /etc/dhcp/inittab.