Hello, I'm not seeing anything in the documentation about what sending a HUP should do to the recursor, but here I'm seeing it kill the process.
It gets a bit stranger than that though… We had a log rotation rule setup that was sending the recursor a HUP at midnight. This was unneeded since syslog is how pdns logs, so I'm not sure why we even had that there. That said, two identical boxes (same hardware, OS+version, same build of the same recursor pkg) were acting differently. The one that died on a HUP was where I was originally fiddling with controlsocket owner/location/mode, the one that did not die on a HUP was untouched, just running with defaults. Removing the socket after stopping the recursor and letting it set perms itself resulted in mode 700 and both now die on a HUP. However trying 750 and 755 is not "fixing" it. I'm suspicious of the socket owner/perms only because that's the only thing I know was originally different between the two boxes. Setting "trace=on" in the config file gives me no further information. In both cases the recursor just exits without logging anything. OS is FreeBSD 8.3, recursor is 3.3. What else can I look at to track this down? Thanks, Charles -- Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet www.bway.net [email protected] - 212.655.9344 _______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
