This is probably very old, but it's new to me.
yosefk> bk pull
... wait ...
/usr/X11R6/bin/xauth: timeout in locking authority file
/homes/yosefk/.Xauthority
... go ahead ...
1. Why does bk lose this way, unlike other commands working with remote
machines?
2. Why did it work for years and stopped now?
3. The part I really like: if bk (or whatever it spawns down it's guts)
*successfully proceeds* after reaching this timeout, wouldn't it be a nifty
optimization to go ahead without even *trying* to lock the "authority" file,
whatever that means?
My admin suggested One Hell of a Workaround: `unsetenv DISPLAY`. That surely
handles the timeout and is especially useful in scripts running bk. Somewhat
tiring in interactive sessions though.
