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

2010-12-01 Thread Karsten Bräckelmann
On Mon, 2010-11-29 at 21:11 -0600, Matthew Barnes wrote: > On Mon, 2010-11-29 at 22:11 -0430, Patrick O'Callaghan wrote: > > '--force-shutdown' has always seemed to me a kludge, effectively a tacit > > admission that the GUI can sometimes freeze and not listen to Quit. I > > hope we can get to a po

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

2010-12-01 Thread Pete Biggs
On Tue, 2010-11-30 at 18:43 -0600, Matthew Barnes wrote: > On Tue, 2010-11-30 at 14:05 -0430, Patrick O'Callaghan wrote: > > AFAIK killev used to be exactly the same as --force-shutdown. Not sure > > about now though. > > That's still true. In UNIX terms, the evolution process exec()'s (or > beco

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

2010-11-30 Thread Matthew Barnes
On Tue, 2010-11-30 at 14:05 -0430, Patrick O'Callaghan wrote: > AFAIK killev used to be exactly the same as --force-shutdown. Not sure > about now though. That's still true. In UNIX terms, the evolution process exec()'s (or becomes) killev when --force-shutdown is given.

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

2010-11-30 Thread Patrick O'Callaghan
On Tue, 2010-11-30 at 14:08 +, Pete Biggs wrote: > I should also mention here that the command 'killev', which does a > similar thing as --force-shutdown also leaves the component processes > running. AFAIK killev used to be exactly the same as --force-shutdown. Not sure about now though. po

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

2010-11-30 Thread Patrick O'Callaghan
On Tue, 2010-11-30 at 08:34 -0500, Adam Tauno Williams wrote: > On Mon, 2010-11-29 at 21:11 -0600, Matthew Barnes wrote: > > On Mon, 2010-11-29 at 22:11 -0430, Patrick O'Callaghan wrote: > > > '--force-shutdown' has always seemed to me a kludge, effectively a tacit > > > admission that the GUI can

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

2010-11-30 Thread Pete Biggs
On Tue, 2010-11-30 at 08:34 -0500, Adam Tauno Williams wrote: > On Mon, 2010-11-29 at 21:11 -0600, Matthew Barnes wrote: > > On Mon, 2010-11-29 at 22:11 -0430, Patrick O'Callaghan wrote: > > > '--force-shutdown' has always seemed to me a kludge, effectively a tacit > > > admission that the GUI ca

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

2010-11-30 Thread Adam Tauno Williams
On Mon, 2010-11-29 at 21:11 -0600, Matthew Barnes wrote: > On Mon, 2010-11-29 at 22:11 -0430, Patrick O'Callaghan wrote: > > '--force-shutdown' has always seemed to me a kludge, effectively a tacit > > admission that the GUI can sometimes freeze and not listen to Quit. I > > hope we can get to a p

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

2010-11-29 Thread Matthew Barnes
On Mon, 2010-11-29 at 22:11 -0430, Patrick O'Callaghan wrote: > '--force-shutdown' has always seemed to me a kludge, effectively a tacit > admission that the GUI can sometimes freeze and not listen to Quit. I > hope we can get to a point where it's no longer necessary. I don't see > similar options

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

2010-11-29 Thread Patrick O'Callaghan
On Mon, 2010-11-29 at 21:23 -0500, Adam Tauno Williams wrote: > > If not, then surely the '--force-shutdown' > > option has rather lost its potency. > > Hopefully this is temporary. [?] '--force-shutdown' has always seemed to me a kludge, effectively a tacit admission that the GUI can sometimes

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

2010-11-29 Thread Adam Tauno Williams
On Mon, 2010-11-29 at 22:52 +, Pete Biggs wrote: > On Mon, 2010-11-29 at 15:32 -0600, Matthew Barnes wrote: > > On Mon, 2010-11-29 at 09:52 +, 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

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

2010-11-29 Thread Pete Biggs
On Mon, 2010-11-29 at 15:32 -0600, Matthew Barnes wrote: > On Mon, 2010-11-29 at 09:52 +, 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"

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

2010-11-29 Thread Matthew Barnes
On Mon, 2010-11-29 at 09:52 +, 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.

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

2010-11-29 Thread Kip Warner
On Mon, 2010-11-29 at 09:52 +, Pete Biggs wrote: > (Evo 2.32.1 on Fedora 14) > > 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 >

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

2010-11-29 Thread Pete Biggs
(Evo 2.32.1 on Fedora 14) 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 (whi