[6933] in testers

home help back first fref pref prev next nref lref last post

Re: install/update of 9.4

daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon May 2 12:23:50 2005

From: Greg Hudson <ghudson@MIT.EDU>
To: Jonathan Reed <jdreed@mit.edu>
Cc: testers@mit.edu
In-Reply-To: <p05230101be9bef810d7d@[18.152.1.192]>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1115050953.17500.243.camel@egyptian-gods.mit.edu>
Mime-Version: 1.0
Date: Mon, 02 May 2005 12:23:38 -0400

On Mon, 2005-05-02 at 11:00, Jonathan Reed wrote:
> And, it happened again.  This was the first login immediately 
> following a cold boot of the machine, so I don't quite understand 
> what dustbuster was doing there:

dustbuster being there is expected.  It runs when the gconfd process is
first started and (in theory) attempts to clean it up when the session
ends.

> Attaching to process 2945 and backtracing gives:
[...]
> #1  0x001e753c in __close_nocancel () from /lib/tls/libpthread.so.0

> The session finished intializing after I detached from the process, I 
> don't know whether that was expected or not (I haven't used gdb much 
> outside of Xcode)

This experience mirrors mine and Bob Basch's: the process is doing a
close() at the time of attach, and unsticks immediately when the process
is attached to and detached.  The precise location of the close()
varies.

> And that dustbuster process was still sticking around, even after 
> login finished.

A bug, but an unrelated one.


home help back first fref pref prev next nref lref last post