Thank you all.
Initially, I was using the --restart option when calling evolution-
backup so I would have assumed that it would have its own internal
timing on this. I'll try issuing the evolution --quit command from a
terminal window and give evolution some time, and see what it does, as
per Ralf's suggestion.
Andre's explanation of some distributions disabling behaviour seems the
most likely, especially as the people behind the Mint distribution seem
to be cautious about the versions they bundle.
If all else fails, I'll use Michael's code.
Many thanks for the help.
Michelle.
On Sun, 2019-06-02 at 13:26 +0200, Ralf Mardorf via evolution-list
wrote:
> On 02 Jun 2019 12:55:00 +0200, Michael Hirmke wrote:
> > _me=$( basename $0 )
> > EVOL="evolution"
> >
> > killevolution() {
> > $EVOL --force-shutdown
> > sleep 1
> > _pid=""
> > _pid=$( \
> > /usr/bin/ps -wwfe \
> > | grep -i "${EVOL}" \
> > | grep -v "grep" \
> > | grep -v "${_me}" \
> > | grep "^${USER}" \
> > | awk '{ print $2 }' \
> > )
> > if [ -n "$_pid" ]
> > then
> > for _p in $_pid
> > do
> > kill $_p
> > done
> > fi
> > }
>
> Ok, a signal 15 might imply that it doesn't matter in what order to
> kill
> evolution related processes, OTOH 'if...then' without verifying that
> the
> processes are gone away, before continuing, gains nothing at all.
> Even
> if you would send a signal 9, you should test, if the process is
> already killed, before continuing. Even much unlikely race conditions
> do
> happen very often.
>
> _______________________________________________
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
