Making unbound-anchor very verbose

[Edward Lewis]

Thanks.  That has kicked me off in some direction.

On 9/21/15, 11:02, "Unbound-users on behalf of unbound-users at unbound.net"
<unbound-users-bounces at unbound.net on behalf of unbound-users at unbound.net>
wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>Hi Ed,
>
>It does not say a lot because all it does is do an UDP query, see that
>it works, and exit.  If you add, say, -F (force TLS update), then
>it'll print out a lot of info (with -vvvv).  Like, https headers, ssl
>certificates, xml contents ...
>
>Best regards, Wouter
>
>On 14/09/15 18:56, Edward Lewis via Unbound-users wrote:
>> D'oh - smallapp/...
>> 
>> On 9/14/15, 12:04, "Edward Lewis" <edward.lewis at icann.org> wrote:
>> 
>>> I'd like to have unbound-anchor be (able to be) much more
>>> verbose.
>>> 
>>> $ unbound-anchor -a testroot.key $ unbound-anchor -a testroot.key
>>> -v testroot.key has content success: the anchor is ok $
>>> unbound-anchor -a testroot.key -vvvvv testroot.key has content
>>> success: the anchor is ok $ unbound-anchor -a testroot.key -v -v
>>> -v -v testroot.key has content success: the anchor is ok
>>> 
>>> I.e., the latter two ought to "show the work done."  I'm more
>>> interested in the process than obtaining the result (so long as
>>> the result is as expected).
>>> 
>>> 
>>> I'm not too familiar with unbound distributions.  Where (in what
>>> files) can I add print/echo statements to do this?  (I don't have
>>> specific statements to add, I need to prototype it.)  I just
>>> don't read script well enough I guess. ;)
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v2
>
>iQIcBAEBCAAGBQJWABwHAAoJEJ9vHC1+BF+Neb8P/jSBaxli4sPh8Ip2amMPo+7I
>fT4FLX17Rgld6kbgG0KPKSpFI2vCCO+n/L98naqKSKwSZdDEyKDDQ80C2ARxLfuB
>v1oFQRtDY4+FHpmIyhzbAVMz1Q0Ghs7VQvcpAJbTv5s0L+Gj6ZwoG8TmNb8rdG1A
>GAoS2BZBC/Gb0WRsR5e9ZlkjV8i5jGDEFYybiNvGnrsc4HKZjPXOO7/EJlEGNjtX
>EhYTrCm2XrvNIQx9Gm4b2OyGbUmsM6RsJZc6IDLyKFrHnC2Uo1VOulx2bLj1ekHl
>g5ZifUimdluPJ5zeItSGpPtAxGFunA+N2l2D1ydph3S4Ov5o1yneWf4pbA9OSwJo
>/gRChnRLzNFFEVu3CDJLlOQjHLo48Hxj5K87kuJmK301bVuhhnPzKHXu+O2qlSX9
>IyQPzMatG+XgM+hPg4N2OEJegoq6cCLANV4y9klvQ6tIGGl29185ZPI4Nz4h2FCB
>+fWSz8/rEbpmAnbetg5Vl2hR5gJD8+Dbh29HAGZEw2YSbNAY0nXr6A7bXDmL1oRc
>2Na4kp0VhsPK2ErK+gXCbL1hyYYaRQIJmVaw0+9y8CA6wGw5Lgfz6CbYGaV/HA6s
>ihiWSVH0751WUNWl+2BrBR1xzK5sS1kduDirPdFBz5iSRmy1eMpWONqQ6G70TmDh
>eAwS32SX1p/Gn/l0jY+K
>=Sd/Z
>-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4604 bytes
Desc: not available
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20150922/410f290f/attachment.bin>