You are not logged in.
I haven't used Evolution much, so I only recently noticed that when launched, the following additional processes are started:
- evolution-alarm-notify (~10 MB RAM)
- evolution-data-server-1.12 (~7 MB RAM)
Fine, I suppose.
However, I also noticed that upon closing Evolution, those components / processes are not terminated. I do not need or want them running full-time. I don't know if the behavior has been compiled into the Evolution binary purposefully or whether it is a bug or something else. I also:
- searched for an editable Evolution startup-script on the system which may specify the components to be launched (using the '--component' option, perhaps), but I couldn't fine anything;
- checked gconf-editor and came up empty;
- checked Evolution preferences, and did not find anything relevant;
- de-selected plug-ins to check for correlation, but found none;
- checked available command-line options, but there was nothing helpful for automatically forcing termination of all components when Evolution is terminated via its GUI.
Anyone have any ideas how to prevent these processes from continuing to run using a simple, direct solution? Hopefully, I have overlooked something obvious. By the way, I am using Gnome 2.20 (Evolution 2.12.1-1).
Thank you.
----
I have written a script to take care of the "rogue" processes until a more direct approach is identified, but it seems like such a script should not be required. I have posted the script for anyone interested. The recommended use is to create an Application Launcher for the script. Clicking the Launcher icon the first time will launch Evolution and clicking the Launcher the second time will terminate Evolution PLUS its related processes.
#!/bin/bash
# AUTHOR: Anonymous
# VERSION: 1.0
# LICENSE: n/a
# Date: 2007 10/23
# REQUIRES: pidof, ps, kill
# SCRIPT NAME: evo_toggle
# DESCRIPTION: Toggles launch / close of evolution. On close, stray processes,
# evolution-alarm-notify (EAN) and evolution-data-server-* (EDS),
# are also terminated.
# Note: Terminating EAN may terminate EDS, but some failures have been
# noted. As such, EDS is explicity killed.
# Usage: evo_toggle [PARAMETER]
# Parameters:
# -e terminate all 'evolution' components using 'evolution'
# option, '--force-shutdown'
#
# -k terminate 'evolution' components using 'kill' command
#
# Note: if run without explicit parameter, behavior is equivalent
# to '-e' parameter
#=============
# Variables - Main
evopid="$(pidof -s evolution)"
launch="evolution"
# Variables - Parameters
altkill="$1"
# Main
if [ -z "$evopid" ] ; then
$launch &
elif [ -n "$evopid" ] ; then
case "$altkill" in
'') # (default) kill 'evolution' components via built-in 'evolution' option
killitevo="evolution --force-shutdown"
echo "Running command: $killitevo"
$killitevo &
wait
;;
'-e') # kill 'evolution' components via built-in 'evolution' option
killitevo="evolution --force-shutdown"
echo "Running command: $killitevo"
$killitevo &
wait
;;
'-k') # kill 'evolution' components via 'kill' command
alarmpid="$(pidof -s evolution-alarm-notify)"
serverpid="$(ps xco pid,cmd | grep 'evolution-data' | cut -d" " -f1)"
killitpid="kill -15 $evopid $serverpid $alarmpid"
echo "Running command: $killitpid"
$killitpid &
;;
esac
fi
exitOffline
evolution-data-server 1.12.1 fixes this and it exists with gnome-session. Previous versions would still be running even after you quit your gnome-session.
Last edited by hussam (2007-10-23 20:36:37)
Offline
evolution-data-server 1.12.1 fixes this and it exists with gnome-session. Previous versions would still be running even after you quit your gnome-session.
Thanks for the info.
Last edited by MrWeatherbee (2007-10-23 20:46:51)
Offline