Maintained by: NLnet Labs

[Unbound-users] which module inform_super callback was called in when the execution path is mesh_make_new_space()->mesh_walk_super()?

W.C.A. Wijngaards
Mon Oct 17 11:25:46 CEST 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Yang,

On 10/17/2011 09:21 AM, Yang Zhe wrote:
> I'm reading the source code of unbound to see if I can write my own
> module who does similar things to your pymod.
> 
> When I'm managing to know what should I do in inform_super callback, I
> find that there are two situations it will be called:
> 
> a) qstate finished, the inform_super of module 0 will be called
> b) qstates kicked out by mesh_make_new_space(), mesh_walk_super()
> calls the inform_super of s->curmod
> 
> Could anybody tell me what should I do in inform_super in the second case?

It is removed because it failed, you are informed that the qstate stops
because of the error.

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOm/SaAAoJEJ9vHC1+BF+N31QP/3bXz+GycnwH93wPC74Y0EZk
LkBFJLQCAjEQUff4XzozFWZm7FAH+EeOTMawaruo4FRq/MZlxKyV1C80sElw2Ip3
gSlQcIjfEUY8OaMz5hpIRftfI95nv7FpYVum7B04H9Jng8sadUIVDCFIhT7L96Bt
K8Kfep1Iz6SSmb+g0Xone6gCpysfB0LT6g7SnGgE/6rSBPxNxuU5OTzli2hyIUFu
vLcPyGQO5XMZEiEzxJSD5ijyY7wxPqQuW98rYl4mVimnRjH+o1TksEGsxfV5HqU3
nhtSdOxsKt7e8uvgsUQ7YPNe8jUUg7CUFz6NA5Ztet4lgy9Qb7nDUbaWBSg4ff47
ZtK4Eo1cgM/EtXOZlXrtPNcLw6MEp2jZgQJI0ATyFkSkjkQ9ojVgmVCEtPlqrhMz
DTE//c5gkCUBsYJF+POukr8etPY0sgeKZihqSlubQsWntof2wIIGnl0FkwbB2KWF
oCSIilVMzcfVGazO9q235EYYWKSCPxqgFqcbxZSD1ic6JI/iIuM1y3CeYdxf73eS
W7P2sM7ZoVAub+g2wIskyC7JOlAmnEJpuTLfCIIogO1vswhJnsQwOWlXYi2oepfg
WMiCSQDZ//ogsjBbLX2IZ1OiCXD8qh0ud7t2YnQNEVSjcXPVEkuIA0sRE9SYHX2C
YVtsU92/5KThJaIIIFBx
=Hh+J
-----END PGP SIGNATURE-----