[OpenAFS] Re: Continuing problems with aklog on Mac OS X (rc10), internal state confused?

[Marcus Watts]

Adam Megacz <megacz@cs.berkeley.edu> writes:
> How do I stop afsd from forking into the background?  Just launching
> "afsd &> foo" doensn't get me much.

You don't.  afsd is highly magical.  It forks a bunch of times,
and most of the pieces dive into the kernel and never return.
The userland thread that does dns upcalls is highly unusual.
Using syslog is probably your best bet, but if you wanted
to do more serious debugging on this, you may want to pull
out "gdb".  It's possible that attaching gdb to the correct afsd
process will work.  Alternatively, you might find it easier
to make a special version of afsd that is split into two pieces:
	- afsd which does everything *except* the dns up calls.
	- a separate program that does *only* the dns up calls.
You might need to tweak the cache manager a bit to do this
nicely, but in theory you should be able to kill the separate
dns handler and restart a new changed copy (assuming it
doesn't need to keep local state.)

				-Marcus