After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 253484 - EDS Should Have a --force-shutdown
EDS Should Have a --force-shutdown
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: general
pre-1.0 (obsolete)
Other All
: Normal normal
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks: 327516
 
 
Reported: 2004-01-28 21:20 UTC by Dan Berger
Modified: 2013-09-10 13:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dan Berger 2004-01-28 21:20:59 UTC
Description of Problem:

Ive had several instances where evo dies and refuses to re-start.  In each
case, running --force-shutdown doesn't help - and the culprit turns out to
be a still-running evolution-data-server.

--force-shutdown should clean up this process as well.
Comment 1 Rodney Dawes 2004-01-29 14:45:45 UTC
Since evolution-data-server is nominally totally separate from
Evolution itself, having Evolution kill it when there is something
wrong with Evolution, is silly, since other apps may need the server.
However, having evolution-data-server have a --force-shutdown option
so that it may dispose of itself, and any backends, would probably be
a good thing. Then, one could just run
/usr/libexec/evolution-data-server-1.0 --force-shutdown to kill the
server and any out-of-process backends.
Comment 2 JP Rosevear 2004-08-03 21:26:08 UTC
Evolution does kill this now, further enhancements can happen post 2.0
Comment 3 André Klapper 2005-09-28 11:49:08 UTC
retargetting from 1.3 to 1.5 to get rid of that busted milestones (as discussed
with harish on irc).

reassigning to harish.
Comment 4 André Klapper 2006-01-09 00:37:53 UTC
also see bug 323115 and bug 253904
Comment 5 André Klapper 2006-06-18 20:42:32 UTC
one can nowadays shutdown evolution-data-server by running "evolution --force-shutdown", see bug 323115, so i'm closing this as obsolete.