Aaron Crane wrote:
My guess is that this is related to the crash you recently vented hate about: something left some locks lying around, and now xauth is confused by them. Assuming that's true, `man xauth` suggests that:
Probably not exactly that, since the problem preceeded the crash (started several weeks ago). Maybe something else crashed on this happy network of ours. Go figure. For example, bk itself is quite fond of lock files. Press Ctrl-C right after `bk push`, and noone else will be able to interact with your parent repository, since the write lock file is there to stay until someone sshs to the host and bk unlocks it (which AFAIK works independently of whether the locking process is still around or not).
Lock files. An industry Best Practice (tm).
Though I didn't know until just now that X authority files ever got locked, so I could be wrong.
Not only do they apparently get locked - they also appear to get locked for no particular purpose except for the fun of locking by itself, since the damned program works after reporting it's inability to enjoy the locking of a file.
smime.p7s
Description: S/MIME Cryptographic Signature
