On Fri, Jul 11, 2014 at 08:23:34PM -0400, Barry Margolin wrote: > BIND already assumes mtime is reliable -- if you do "ndc reload", it > only reloads zone files whose mtimes are newer than when the zone was > previously loaded.
Of course, but it *checks them for validity* when it loads them. If the file's corrupt, it logs an error and carries on serving the previous version. With map files, we had a choice: a) check validity during load (which takes a bit time), b) mmap() into memory without validating, and hope really hard that the file isn't corrupt (which gives you near-instant server startup, but could cause assertion failures or serve bad data if there was a problem), or c) mmap() the file into memory without validating, and rewrite named to cope robustly with zone database corruption if it's detected later on (which turns out to be Hard). We decided to spend the time and validate map files before serving data from them. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
