Re: to alarm or not to alarm (was: Re: [Evolution] Completely unload Evolution from memory.)
- From: "Panos Tsapralis (TELLAS)" <ptsapralis tellas gr>
- Cc: EVOLUTION Mailing List <evolution lists ximian com>
- Subject: Re: to alarm or not to alarm (was: Re: [Evolution] Completely unload Evolution from memory.)
- Date: 22 Jul 2003 20:21:21 +0300
On Tue, 2003-07-22 at 18:21, Rodrigo Moya wrote:
On Tue, 2003-07-22 at 00:09, guenther wrote:
which processes are those? evolution-wombat and evoution-alarm-notify
should always be running.
I just wondered (nope, not using alarm normally):
As these processes have to be running for notifying the user, shouldn't
they be launched on login?
As they are not running on login, the user will not be notified unless
he actually runs Evolution -- at least for a short time.
if you start evolution on a GNOME session, when closing the session, the
list of running programs is saved, so the alarm daemon should be started
if it was running when the session was ended.
What if I don't use Evolution within Gnome? Then I am at a loss, am I
Isn't it working that way for you?
No, it's not, not for me, anyway, since I am not using Gnome (I do not
want to spend my valuable system resources to useless things, hence I
The question remains: is there any way to start this calendar alarm
function in "daemon" mode, so that I do not miss any alarms before
logging into Evolution for the first time?
If there is not any such way, it would be nice to add the feature
sometime in the future (I have to admit, however, that this is in no way
of high priority...).
evolution maillist - evolution lists ximian com
Panos Platon Tsapralis,
Software Engineer, SAP-R/3 specialist,
Registered Linux User #305894,
Ximian Evolution (ver.1.4) on Red Hat Linux (8.0),
cell-phone: +306946462857, fax: +302108054420,
e-mail: panosplaton in gr, panosplaton hotmail com
] [Thread Prev