Re: [Evolution] --force-shutdown doesn't close all Evo processes on 2.32

[Adam Tauno Williams <awilliam whitemice org>]

On Mon, 2010-11-29 at 22:52 +0000, Pete Biggs wrote: 
> On Mon, 2010-11-29 at 15:32 -0600, Matthew Barnes wrote:
> > On Mon, 2010-11-29 at 09:52 +0000, Pete Biggs wrote:
> > > I noticed this morning that my system was running low on memory and the
> > > main culprit seemed to be e-calendar-factory at about 1.5G (!).  So I
> > > used "evolution --force-shutdown" to try and clear up all the Evo
> > > processes but it didn't work.  It tried to close evolution (which it
> > > couldn't find because it wasn't running), but didn't shutdown any of the
> > > associated backends.
> > > Is this expected behaviour?
> > It's expected behavior but not quite the desired behavior.
> > See: https://bugzilla.gnome.org/show_bug.cgi?id=590245
> > The D-Bus services still need some kind of shutdown method so they can
> > terminate gracefully when asked, rather than just up and killing them
> > like we used to under Bonobo.  We already do this for Evolution.
>
> Sorry, I don't understand.  Are you saying that the various factories
> should have been terminated?  

Ideally, yes.  But ith the move from Bonobo to D-Bus and that
functionality seems not to be there yet.

> If not, then surely the '--force-shutdown'
> option has rather lost its potency.  

Hopefully this is temporary. [?]

> What is the approved way of killing the D-Bus services now?

I currently kill -15 on the rare occasion I need to whack Evolution.