summaryrefslogtreecommitdiff
path: root/src/reply-password
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2015-11-26 23:33:55 +0100
committerLennart Poettering <lennart@poettering.net>2015-11-27 00:03:39 +0100
commitc3bc53e62459d7e566ffffeade41cd82bc6754f5 (patch)
tree493af39bae9bfb965a3a2675456baeb111f1d331 /src/reply-password
parentae6a4bbf318e197813227e50c245a00de03784a2 (diff)
resolved: for a transaction, keep track where the answer data came from
Let's track where the data came from: from the network, the cache or the local zone. This is not only useful for debugging purposes, but is also useful when the zone probing wants to ensure it's not reusing transactions that were answered from the cache or the zone itself.
Diffstat (limited to 'src/reply-password')
0 files changed, 0 insertions, 0 deletions