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.
Perhaps verifying that everything is killed by running
pgrep -a evolution
is a good idea?
And after that starting evolution with redirecting all output to a log
file. Since the login shell most likely is bash
evolution &>/tmp/evolution.log)
Regards,
Ralf
_______________________________________________
evolution-list mailing list
[email protected]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
