>>>>> >>>> >>>> The kerberos key isn't causing the problem. >>>> >>>> >>>> >>>>> >>>>> b..s is happening this should not produce >>>>> this miserable kernel loop that kills the most powerful machines >>>>> available >>>>> today, it either should have some slower cadence so that eventually >>>>> some >>>>> could stop the AFS processes or it should give up after some time, I >>>>> this >>>>> regard I consider this behavior a bug. >>>>> >>>>> >>>> >>>> it probably is. >>>> >>>> dumb question: are you using dynroot? >>>> >>>> >>> >>> Actually yes, I do, and it works like a charm, is that bad now ?!?!?!? >>> >> >> sure. it means you're starting afs with no servers available to serve >> root.afs. >> >> it's a bug. there's a ticket open for it. but it's easily avoidable: >> don't do that. >> > > Oh well, fashion changes, some while ago NOT USING dynroot was bad and > obsolete, now is vice-versa ;), good to know that this was what was causing > it > but then again dynroot is quite convenient, I hope the bug gets fixed > sometime. > Thank you Derrick for your quick and informed answers, you're a life savior > for us not so gurus in the matter :).
Actually, stop thanking me, I think I was confused, and just confused you. dynroot is good, is what you want. Don't disable it. As to the apparent infinite loop: i take it nothing makes it to the kernel message log, and you have no way to grab a kernel task list? (alt-sysrq-t) -- Derrick _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
