On Jan 2, 2011, at 10:59 PM, Ryan Schmidt wrote: > > daemondo is a part of MacPorts base. MacPorts uses it for all launchd plists > it creates, though probably most software doesn't need it. I think it's > needed for those ports whose daemons do not offer the option not to daemonize > (which as discussed previously would be a problem for launchd); in that case, > daemondo can monitor a pid file instead.
daemondo can also monitor for system configuration changes and act on them (so for named, it can restart when the network changes). >> The interesting issue for named is that when running with the "-f" option >> it apparently "invokes" or otherwise "prevents" >> certain kinds of logging. >> >> From: http://www.bind9.net/manual/bind/9.3.2/Bv9ARM.ch06.html#id2553006 >> ------------------<cut here>-------------------------------------- >> channel default_debug { I guess 'default_debug' is special [the docs also say it only gets used when debugging is turned on]? I've used something like this for forever: logging { Channel named_log { file "/var/log/named.log" versions 3 size 20m; print-time yes; severity notice; }; category default { named_log; }; category queries { named_log; }; }; You can unload/load, kill named (HUP or TERM), or use rndc to control the bind9 port. I usually use HUP since I've been doing that since before rndc ;-) -- Daniel J. Luke +========================================================+ | *---------------- [email protected] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
