Re: [Evolution] killev doesn't kill all associated processes

["Jason A. Pfeil" <pfeil 10East com>]

These are GNOME processes, not Evolution processes.  All evolution
processes start with "evolution" in their name.  Since evolution uses
CORBA through ORBit, oafd needs to be started to allow for the
activation of various Evolution and other GNOME objects.  Gconfd is the
GNOME configuration daemon that maintains an in-core and on-disk
database of user and system configuration settings.

--Jason

On Mon, 2002-03-11 at 04:57, Paul Hands wrote:
> When I use killev to remove all the evolution processes, it leaves two
> alive every time...
>  
> oafd --ac-activate --ior-output-fd=10
> gconfd-1 --oaf-activate-iid=OAFIID:gconfd:19991118 --oaf-ior-fd=20
>
> Sometimes, when I've made changes to my evo configuration, I find they
> don't seem to take effect unless I kill these processes too.
> Does anyone know why they get left alive?
>
> Thanks,
>
> Paul
-- 
Jason A. Pfeil                        pfeil 10East com
Senior Open Systems Engineer          http://www.10East.com
10East, Inc.                          (904)220-DOCS