projects / platform / upstream / systemd.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ae6a4bb) | patch
resolved: for a transaction, keep track where the answer data came from
authorLennart Poettering <lennart@poettering.net>
Thu, 26 Nov 2015 22:33:55 +0000 (23:33 +0100)
committerLennart Poettering <lennart@poettering.net>
Thu, 26 Nov 2015 23:03:39 +0000 (00:03 +0100)
commitc3bc53e62459d7e566ffffeade41cd82bc6754f5
tree493af39bae9bfb965a3a2675456baeb111f1d331tree | snapshot
parentae6a4bbf318e197813227e50c245a00de03784a2commit | 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.
src/resolve/resolved-dns-scope.c diff | blob | history
src/resolve/resolved-dns-transaction.c diff | blob | history
src/resolve/resolved-dns-transaction.h diff | blob | history
Domain: System / System Framework;