doc/*: tai64nlocal comes from daemontools, not djbdns.

[djbdns-logparse.git] / doc / man1 / djbdns-logparse.1

diff --git a/doc/man1/djbdns-logparse.1 b/doc/man1/djbdns-logparse.1
index 05e6c7530c724263f66ad1e9d96e79d3a72a9eda..fc546e9935f9f739de17b39b798ddd73dd903269 100644 (file)
--- a/doc/man1/djbdns-logparse.1
+++ b/doc/man1/djbdns-logparse.1
@@ -83,7 +83,7 @@ Rob Mayoff's notes on the dnscache log file format
 The following transformations are common to  both daemons' logs:
 .IP \(bu 2
 The leading timestamps are piped through the
-\fBtai64nlocal\fR program.
+\fBtai64nlocal\fR program from DJB's daemontools.
 .IP \(bu
 IPv4 addresses are converted from hexadecimal strings to decimal
 dotted-quads; for example \(dq7f000001\(dq becomes \(dq127.0.0.1\(dq.
@@ -97,8 +97,7 @@ The query type id is converted to the corresponding RFC-defined type
 name, as in https://en.wikipedia.org/wiki/List_of_DNS_record_types.
 While dnscache logs the id in decimal, tinydns records it in
 hexadecimal (for example, \(dq001c\(dq) necessitating a hex->decimal
-conversion before we can look up its name. Decimal numbers with
-no entry in the id->name mapping are output as-is.
+conversion before we can look up its name.
 
 .P
 The following transformations are specific to tinydns: