On Aug 3, 2006, at 6:18 PM, Joshua Penix wrote:
I'm sure that both find and tmpwatch can take care of the symptom, but I suspect Mike was more interested in the cause. I'm interested as well, since I have one machine which exhibits the same behavior Mike is seeing andI don't believe it's something that BIND typically does. Yes I could just clean up the symptoms, but if the behavior is indicative of some sort of misconfiguration or bug, I'd much prefer to fix that.
Having run multiple BIND servers in environments large and small, I can safely say that these are left over from aborted zone transfers (axfr) attempts. At least, that's the only time I've ever seen them get generated.
If you are running a slave server and can afford a bit of downtime, you'll see these files get created if you blow away the local copies of the zones and re-start named. Zones are copied to temporary files with those naming patterns until the entire axfr is complete and verified. Then, the temp file is copied to the filename specified in named.conf for that zone. If there is an error, and/or the axfr never completes, it's possible for these temp files to be left unreaped.
As proof of this theory, have you looked at the contents?Also, this assumes that my memory of the beginning of this thread is correct, and these files are on a slave server.
Gregory making a couple assumptions -- Gregory K. Ruiz-Ade <[EMAIL PROTECTED]> OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu
PGP.sig
Description: This is a digitally signed message part
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
