HP-UX Reference (11i v2 04/09) - 4 File Formats (vol 8)

g
gated.conf(4) gated.conf(4)
It is not currently possible to specify packet tracing from the command line. This is because a global
option for packet tracing would potentially create too much output.
When protocols inherit their tracing options from the global tracing options, tracing levels that do not
make sense (such as parse, adv and packet tracing options) are masked out.
Global tracing statements have an immediate effect, especially parsing options that effect the parsing of
the configuration file. Tracing values inherited by protocols specified in the configuration file are initially
inherited from the global options in effect as they are parsed, unless they are overridden by more specific
options. After the configuration file is read, tracing options that were not explicitly specified are inherited
from the global options in effect at the end of the configuration file.
Packet tracing
Tracing of packets is very flexible. For any given protocol there are one or more options for tracing pack-
ets. all protocols allow use of the packets keyword allows for tracing all packets sent and received by the
protocol. most protocols have other options for limiting tracing to a useful subset of packet types. These
tracing options can be further controlled with the following modifiers:
detail detail must be specified before send or recv. Normally packets are traced in a terse
form of one or two lines. When detail is specified, a more verbose format is used to pro-
vide further detail on the contents of the packet.
send
recv These options limit the tracing to packets sent or received. Without these options both
sent and received packets will be traced.
Detail, if specified, must be before send or recv. If a protocol allows for several different types of
packet tracing, modifiers may be applied to each individual type. But be aware that within one tracing
specification the trace flags are summed up, so specifying detail packets will turn on full tracing for
all packets.
Traceoptions syntax
traceoptions ["trace_file"[replace][size size[k|m] files files]]
[control_options] trace_options [except trace_options];
traceoptions none ;
trace_file Specifies the file to receive tracing information. If this file name does not begin with a
slash (/), the directory where gated was started in prepended to the name.
replace Tracing should start by replacing an existing file. The default is to append to an existing
file.
size size[k|m] files files
Limit the maximum size of the trace file to the specified size (minimum 10k). When the
trace file reaches the specified size, it is renamed to file.0, then file.1, file.2 up
to the maximum number of files (minimum specification is 2).
control_options
Specifies options that control the appearance of tracing. Valid values are:
nostamp
Specifies that a timestamp should not be prepended to all trace lines.
except trace_options
Used to enable a broad class of tracing and then disable more specific options.
none Specifies that all tracing should be turned off for this protocol or peer.
Directive Statements
Directive statements provide direction to the GateD configuration language parser about included files
and the directories in which these files reside. Directive statements are immediately acted upon by the
parser. Other statements terminate with a semicolon (;), but directive statements terminate with a new-
line. The two directive statements are:
%directory "directory"
Defines the directory where the include files are stored. When it is used, GateD looks in the
directory identified by pathname for any included files that do not have a fully qualified
filename, such as files that do not begin with "/". This statement does not actually change the
HP-UX 11i Version 2: September 2004 − 5 − Hewlett-Packard Company Section 4−−81