When auth is enabled, certain log operations aren't as informative as they might be. For example, the warning about not yielding because the recursive lock is held tries to get the current op's info, which is only available to threads authenticated to the admin db, so the warning message reports 'top:

'.

So maybe log messages should make a practice of bypassing auth checks of this sort, so long as we're only sending log output to files and other things that only ops folks can get at.