On Sun, 2003-05-11 at 12:01, H du Plooy wrote:
Hi all,
If you use evolution from KDE, it starts up a number of background services:
1283 ? S 0:00 oafd --ac-activate --ior-output-fd=10 1287 ? S 0:00 wombat --oaf-activate-iid=OAFIID:Bonobo_Moniker_wombat_Factory --oaf-ior-fd=10 1292 ? S 0:00 bonobo-moniker-xmldb --oaf-activate-iid=OAFIID:Bonobo_Moniker_xmldb_Factory --oaf-ior-fd=12 1316 ? S 0:00 evolution-alarm-notify --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory --oaf-ior-fd=17 1664 ? S 0:00 /opt/gnome/bin/gconfd-1 12
These don't shut themselves down after closing Evolution. They stick around. Though this is no serious problem, I'd like to know why they don't terminate, and if there's a way to have evolution klean up after itself, short of writing a script for that.
Thanks Hans
The process are indeed left after evolution is shutdown. To completely shutdown evolution and its related process you will need (as a user is ok) to run: killev and possibly: oaf-slay I can not tell you anything about why these processes remain, but they seem relatively well behaved and do not typically cause problems. -- Ralph Sanford - If your government does not trust you, rsanford@telusplanet.net - should you trust your government? DH/DSS Key - 0x7A1BEA01