I've installed daemontools, ucspi-tcp, and djbdns on my MacBook as DNS
from my DSL provider takes forever to resolve and I used to run
dnscache on Linux with great satisfaction.
Alas, the moment scscan notices I have /service/dnscache, the fan
kicks into gear -- and I see two supervise processes, supervise
dnscache and supervise log, each consuming 95% of CPU.
An additional resource I found on djbdns on Mac OS is
http://matt.simerson.net/computing/dns/djbdns-macosx.shtml
-- it seems to add configs to daemontools:
system "echo 'cc -O2' > conf-cc";
system "echo 'cc -Xlinker -x' > conf-ld";
-- but my daemontools apparently work from stock install, so I guess
this is not as if Im building deficient binaries which suddenly
consume all CPU, or could I?...
I still went ahead to create a StartUp item, am not exactly sure why,
as svscan picked u and started the fan without it just fine! I ended
up deleting /service/dnscache symlink until I can prevent the CPU
debauch.
There's also apparently a darwinports port coming up in googling. But
now I wonder where daemontools sticks svscan and is it safe to
reinstall it in various ways...
Does anybody run dnscache on MacBook, and how's your fan doing? :)
Cheers,
Alexy
|