Files
bind9/lib/dns
Matthijs MekkingandMatthijs Mekking 6756280242 Remove rpz->db_registered
As pointed out in !813 db_registered is sort of redundant.  It is
set to `true` only in `dns_zone_rpz_enable_db()` right before the
`dns_rpz_dbupdate_callback()` callback is registered.  It is only
required in that callback and it is the only place that the callback
is registered.  Therefore there is no path that that `REQUIRE` can
fail.

The `db_registered` variable is only set to `false` in
`dns_rpz_new_zone`, so it is not like the variable is unset again
later.

The only other place where `db_registered` is checked is in
`rpz_detach()`.  If `true`, it will call
`dns_db_updatenotify_unregister()`.  However if that happens, the
`db_registered` is not set back to `false` thus this implies that
this may happen multiple times.  If called a second time, most
likely the unregister function will return `ISC_R_NOTFOUND`, but
the return value is not checked anyway.  So it can do without the
`db_registered` check.
2019-02-22 13:59:10 +01:00
..
2019-02-22 13:59:10 +01:00
2019-02-08 13:54:13 +11:00
2019-02-19 07:57:14 +11:00
2019-01-09 23:44:26 +01:00
2018-11-22 11:51:49 +00:00
2018-11-22 11:52:08 +00:00
2018-11-22 11:52:08 +00:00
2019-02-18 17:40:56 -05:00
2018-11-22 11:52:08 +00:00
…
…
2018-11-28 12:00:16 -05:00
2018-12-11 11:32:24 +01:00
2018-12-11 11:32:24 +01:00
2018-12-11 11:32:24 +01:00
2019-01-09 23:44:26 +01:00
2018-11-22 11:52:08 +00:00
…
…
2019-02-18 17:40:56 -05:00
2018-12-11 11:32:24 +01:00
…
…
2019-01-09 23:44:26 +01:00
…
2018-11-22 11:52:08 +00:00
…
2018-11-22 11:52:08 +00:00
2019-01-31 09:35:49 +01:00
2018-11-22 11:51:49 +00:00
2018-11-14 15:26:27 -05:00
2018-11-14 20:17:04 -08:00
2018-12-11 11:32:24 +01:00
…
…
…
2019-01-30 14:11:12 -08:00
…
2018-12-06 10:29:10 -08:00
2018-11-22 11:52:08 +00:00
2019-01-09 23:44:26 +01:00
…
2019-02-22 13:59:10 +01:00
2018-11-22 11:52:08 +00:00
2018-11-22 11:52:08 +00:00
2018-11-22 11:52:08 +00:00
…
2019-02-19 09:17:03 +11:00
…
…
2018-11-22 11:52:08 +00:00
2018-11-22 11:52:08 +00:00
…
…
…
2019-01-31 09:01:23 -08:00
…
2019-02-18 17:39:08 -05:00
…
2018-12-11 11:32:24 +01:00
…
…
2019-02-22 13:59:10 +01:00
…