On Sun, Sep 10, 2006 at 10:34:24PM +0200, Loïc Minier wrote:
> 
>  4) very broken SESSION_MANAGER (bad value),
>  SESSION_MANAGER="local/bee:/tmp/.ICE-unix/00000" gcalctool
>  => DELAY, tries to connect and fail
> 
>  Could you please report the value of SESSION_MANAGER?  (env | grep
>  SESSION_MANAGER)

Interesting... it turns out my shell's $SESSION_MANAGER is pointing to a socket
that belonged to an older X session.  As to why this happens, my shell was
spawned by a screen session that's much older than my X server (when I have to
restart X I just detach from screen, and later reattach).

However, that doesn't explain the delay.  You can tell the socket is not there
inmediately.  I run it through strace and revealed that it's looping over:

  socket(PF_FILE, SOCK_STREAM, 0)         = 11
  uname({sys="Linux", node="aragorn", ...}) = 0
  connect(11, {sa_family=AF_FILE, path="/tmp/.ICE-unix/6173"}, 21) = -1 ENOENT 
(No such file or directory)
  close(11)                               = 0
  rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
  rt_sigaction(SIGCHLD, NULL, {SIG_DFL}, 8) = 0
  rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
  nanosleep({1, 0}, {1, 0})               = 0

It's calling nanosleep five times (1s each).  Is that really necessary?

-- 
Robert Millan

My spam trap is [EMAIL PROTECTED]  Note: this address is only intended for
spam harvesters.  Writing to it will get you added to my black list.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to