[PATCHES]: Don't check zone files modification after NSD start or after receiving HUP signal

NSD
1

Hi.

I am sending a set of patches, which add options to a configuration file:
diable-zonefiles-check:yes/no - enable/disable check of zone files
modification after NSD start
disable-zonefiles-check-hup: yes/no - disable/enable check of zone
files modification after receiving HUP signal

Our servers hold over 150 000 zones and it is not required big disk
operations (call stat() on each file) after NSD start or receive HUP
signal.
Maybe someone will like these configuration options.

Changes and upgrades are welcome :).

This patches and other patches are also available on my github.
https://github.com/marmolak/nsd-4.0-personal-patches
Maybe they will be interesting and inspirating for someone.

Best regards,
Robin Hack

(attachments)

nsd-4.0b2-disable-zonefiles-check.patch (3.03 KB)
nsd-4.0b2-disable-zonefiles-check-hup.patch (2.95 KB)

2

Sorry, i forgot.Patches are for NSD 4.0beta2.

3

Hi Robin,

Sorry, i forgot.Patches are for NSD 4.0beta2.

Thank you, I have applied your patch, but I have modified it,
it is called 'zonefiles-check: yes' (shorter, and default is yes,
which is easier to understand). One option that disables sighup and
startup checks. "nsd-control reload" still checks all mtimes, even if
option is toggled, because you trigger it manually. Is this a good
way to have both patches that you sent?

Best regards,
   Wouter

4

Hi Wouter.

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

Hi Robin,

Sorry, i forgot.Patches are for NSD 4.0beta2.

Thank you, I have applied your patch, but I have modified it,
it is called 'zonefiles-check: yes' (shorter, and default is yes,
which is easier to understand). One option that disables sighup and
startup checks. "nsd-control reload" still checks all mtimes, even if
option is toggled, because you trigger it manually. Is this a good
way to have both patches that you sent?

Thank you.
Yes. It's the best solution.

Best regards, Robin Hack