On Mon, 2019-06-03 at 09:57 +0200, Milan Crha via evolution-list wrote:
> Michelle, by the way, the "--restart" argument of the evolution-
> backup
> means to start evolution after the backup is done. I'm not sure
> whether
> you do that on purpose. Also, the missing .running file indicates
> that
On Tue, 2019-06-04 at 23:20 +0200, Ángel wrote:
> > In which case I think the argument about how to make sure Evo is
> > stopped before doing a backup is pointless. Just don't stop it.
> >
> > poc
>
> Even if a program is transactional, it only guarantees the state at a
> given point of time.
On 2019-06-03 at 12:47 +0100, Patrick O'Callaghan wrote:
> On Mon, 2019-06-03 at 13:40 +0200, Ralf Mardorf via evolution-list
> wrote:
> > On Mon, 2019-06-03 at 12:06 +0100, Patrick O'Callaghan wrote:
> > > Personally, I don't back up Evolution explicitly. I do back up my home
> > > directory
On Mon, 2019-06-03 at 15:00 +0200, Milan Crha via evolution-list wrote:
> I'd say, generally speaking, that it's the safest to close the
> applications/processes which access the files of the interest before
> doing anything with them (being it backup or restore or ...), to avoid
> conflicts in
On Mon, 2019-06-03 at 12:47 +0100, Patrick O'Callaghan wrote:
> In which case I think the argument about how to make sure Evo is
> stopped before doing a backup is pointless. Just don't stop it.
Hi,
it depends on the actual part of the Evolution.
Talking about Mail, then things which can
On Mon, 2019-06-03 at 14:28 +0200, Milan Crha wrote:
> On Mon, 2019-06-03 at 13:08 +0200, Ralf Mardorf wrote:
> > ls: cannot access '.local/share/evolution/.running': No such file or
> > directory
>
> Hi,
> aha, I see, the .running file had been moved to ~/.config/evolution/,
> but
On Mon, 2019-06-03 at 13:08 +0200, Ralf Mardorf via evolution-list
wrote:
> ls: cannot access '.local/share/evolution/.running': No such file or
> directory
Hi,
aha, I see, the .running file had been moved to ~/.config/evolution/,
but backup-restore didn't reflect that change. I fixed
On Mon, 2019-06-03 at 13:40 +0200, Ralf Mardorf via evolution-list
wrote:
> On Mon, 2019-06-03 at 12:06 +0100, Patrick O'Callaghan wrote:
> > Personally, I don't back up Evolution explicitly. I do back up my home
> > directory every night (using rsnapshot) but this almost always happens
> > while
On Mon, 2019-06-03 at 12:06 +0100, Patrick O'Callaghan wrote:
> Personally, I don't back up Evolution explicitly. I do back up my home
> directory every night (using rsnapshot) but this almost always happens
> while my session is logged in. I have been doing this for years and
> have never lost an
On Mon, 2019-06-03 at 13:08 +0200, Ralf Mardorf wrote:
> On Mon, 2019-06-03 at 09:57 +0200, Milan Crha via evolution-list wrote:
> > the missing .running file indicates that evolution is not running
>
> $ evolution -v; ls .local/share/evolution/.running || ps aux | grep evolution
When running
On Mon, 2019-06-03 at 09:57 +0200, Milan Crha via evolution-list wrote:
> the missing .running file indicates that evolution is not running
$ evolution -v; ls .local/share/evolution/.running || ps aux | grep evolution
evolution 3.32.0
ls: cannot access '.local/share/evolution/.running': No such
On Sun, 2019-06-02 at 20:34 +0200, Ralf Mardorf via evolution-list
wrote:
> my advice is to think over your strategy of doing a backup.
Personally, I don't back up Evolution explicitly. I do back up my home
directory every night (using rsnapshot) but this almost always happens
while my session is
Hi,
On Sun, 2019-06-02 at 20:48 +0200, Ralf Mardorf via evolution-list
wrote:
> Ok, removing '.running' might be something done by 'evolution-
> backup', not by your script. My bad.
right, everything prefixed with "evolution-backup-Message" in the
original post is printed by the
Semi-off-topic:
Bashisms are devil's work. If possible, I try to write "portable"
scripts avoiding anything way-too-non-POSIX, but since I usually don't
waste my time with broken file manager GUIs and instead use command
line, I'm in favour of bashisms for this purpose. Some folks prefer C
alike
On Mon, 2019-06-03 at 00:21 +0200, Ángel wrote:
> Rather than adding a check after every command, I would recommend simply
> adding a call to set -e
#!/bin/bash -e
or what ever else, I only wanted to point out that a backup script
should be safe and somehow be able to either resolve issues or to
Yes, a rename in the same partition should be atomic.
Rather than adding a check after every command, I would recommend simply
adding a call to set -e
and rather than those repeated lines, it can be done with a simple loop:
for i in {5..2}; do
rm -f
>> mv /mnt/tank/users/michelle/backup/mail/4.tar.gz
>> /mnt/tank/users/michelle/backup/mail/5.tar.gz
PPS:
Without doing a strace or using google, IIRC a 'mv' done within a
partitions, is an atomic operation. This doesn't mean that a '&&' alike
approach is _not_ better than just a ';' (';' is
PS
>evolution-backup-Message
Ok, removing '.running' might be something done by 'evolution-backup',
not by your script. My bad.
So to avoid confusion, the following applies:
On Sun, 02 Jun 2019 11:08:37 +0100, Patrick O'Callaghan wrote:
>On Sun, 2019-06-02 at 09:14 +0100, Michelle via
On Sun, 2019-06-02 at 09:14 +0100, Michelle via evolution-list wrote:
> Upgraded my version of Mint, which has...
> Evolution 3.28.5-0ubuntu0.18.04.1
>
> Prior to upgrading Linux Mint, my evolution backup script contained
the
> following...
>
> #!/bin/sh
> export DISPLAY=:0.0
> rm
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
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}"
> killall --wait foo &&
Don't get me wrong, I do _not_ recommend to use a killall SIGTERM over
an app's option for a "soft" shut down of the app.
As a user we might not know what processes to SIGTERM and in which
order, while the developers of an app do know this. IOW a SIGTERM isn't
as evil
Hi Michelle,
>Upgraded my version of Mint, which has...
>Evolution 3.28.5-0ubuntu0.18.04.1
>Prior to upgrading Linux Mint, my evolution backup script contained the
>following...
[...]
>So evolution-backup is reporting the "quit" to evolution, but it
>doesn't appear to be listening. Also, there
> I've tried dropping to a command prompt and just issuing...
> evolution --quit
You shouldn't expect that such a friendly termination, even not if you
would kill via SIGTERM, does stopp the app running immediately, such
commands are intended to allow the app to terminate properly.
If you
On Sun, 2019-06-02 at 09:14 +0100, Michelle via evolution-list wrote:
> Upgraded my version of Mint, which has...
> Evolution 3.28.5-0ubuntu0.18.04.1
>
> Prior to upgrading Linux Mint, my evolution backup script contained
> the
> following...
>
> #!/bin/sh
> export DISPLAY=:0.0
> rm
On Sun, 2019-06-02 at 09:14 +0100, Michelle via evolution-list wrote:
> Any advice please?
I doubt that anyone can give useful feedback without seeing the entire
backup script. Quoting parts of it is not useful.
poc
___
evolution-list mailing list
Upgraded my version of Mint, which has...
Evolution 3.28.5-0ubuntu0.18.04.1
Prior to upgrading Linux Mint, my evolution backup script contained the
following...
#!/bin/sh
export DISPLAY=:0.0
rm /mnt/tank/users/michelle/backup/mail/5.tar.gz
mv /mnt/tank/users/michelle/backup/mail/4.tar.gz
27 matches
Mail list logo
