On Fri, 7 Oct 2005, Kyle Moffett wrote:
I nuked it, and now the module loads fine, but due to a defect in my startup
script I managed to start afsd twice without a /afs directory. Now I'm in
this interesting situation:
That situation is called "boned"
At this point I tried to killall afsd with no luck, even -KILL didn't do
anything. A quick top shows that afsd is now hogging 100% CPU, which I
noticed because all the fans suddenly spun up (yay for multiproc boxen, I can
still work!) I don't know if it was doing this before or after I kill -9'ed
it.
This seems bug-ish, and I suspect I'm going to have to reboot. Once I get
back to a sane state again, I'll let you know how things are going.
It's bug-ish.
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
