-file.
-
-The second file (whose location is determined by drl_configfile) is an XML file
-containing a series of DRL identity specifications. DRL supports two types of
-identities. 1) machine identities: A machine identity is responsible for
-limiting all traffic that leaves a machine, regardless of the traffic's sliver
-of origin. 2) set identities: A set identity is responsible for limiting the
-traffic from a set of slivers or other set identities.
+file that is used to configure identities (discussed below).
+
+Optionally, the ulogd.conf file can contain:
+
+create_htb <int>
+Whether or not ulogd should rebuild the htb hierarchy (when using FPS). 0 will
+not rebuild it, any other value will. Set this to zero when the hierarchy is
+managed externally (for instance, by PlanetLab's node manager). When this is
+set to 0, identities require htb_node and htb_parent properties in the drl xml
+config.
+
+enforce_on <int>
+Whether or not to turn enforcement on by default at startup. 0 for off,
+anything else for on. If unspecified, it defaults to 1. Enforcement can be
+turned on/off at runtime with SIGUSR1.
+
+netem_loss <int>
+netem_delay <int>
+netem_slice <int|ALL>
+
+These specifiy an artifical packet loss rate (%) or delay (ms) and the slice
+xid or the string ALL if it should apply to all slices. These are useful for
+experimentation.
+
+The second file (whose location is determined by drl_configfile) is an XML
+file containing a series of DRL identity specifications. Sending the ulogd
+process SIGUSR2 will cause it to re-read this XML config file. DRL supports
+two types of identities. 1) machine identities: A machine identity is
+responsible for limiting all traffic that leaves a machine, regardless of the
+traffic's sliver of origin. 2) set identities: A set identity is responsible
+for limiting the traffic from a set of slivers or other set identities.