On Wed, 2018-01-03 at 12:43 +0100, Ralf Mardorf wrote: > On Wed, 2018-01-03 at 12:11 +0100, Milan Crha wrote: > > well, the --force-shutdown kills the background processes in the > > correct order, which is important at least in GNOME, where > > gnome-shell's calendar-server process (which provides events in the > > clock popup) restarts evolution-calendar-factory process when it > > disappears, which can have consequences when it's not stopped as the > > last process. > > Thank you, > > so an equivalent to > > evolution --force-shutdown > > while sidestepping usage of "evolution" would be > > pkill -9 evolution && killall -9 evolution-calendar-factory > ^^ > I wonder if "-9" anyway would require > "&& sleep 5 &&" or a loop, so probably > "evolution --force-shutdown" is the easiest way, as > long as launching "evolution --force-shutdown" > shouldn't cause an issue itself.
I've never had a problem with 'evolution --force-shutdown'. AFAIK it just calls /usr/libexec/evolution/killev. > Perhaps verifying that everything is killed by running > > pgrep -a evolution > > is a good idea? I use 'pgrep -f ...' as it also lists processes which have changed the first word in their command line (firefox does this for example). poc _______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
