lacking authority

[prev] [thread] [next] [lurker] [Date index for 2007/01/10]

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.

• lacking authority Yossi Kreinin 14:31 on 10 Jan 2007
  • Re: lacking authority Aaron Crane 15:00 on 10 Jan 2007
    • too deep to show
  • dom (Dominic Mitchell) 15:24 on 10 Jan 2007
    • too deep to show
  • David King 17:58 on 10 Jan 2007
    • too deep to show
  • Nicholas Clark 12:49 on 11 Jan 2007
    • too deep to show
• Richard Clamp 17:14 on 10 Jan 2007
  • Martin Ebourne 17:20 on 10 Jan 2007
• Peter da Silva 17:34 on 10 Jan 2007

Generated at 00:01 on 12 Jan 2007 by mariachi 0.52