From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to synchronise between 2 locations
Date: Fri, 29 Mar 2024 12:24:34 +0100 [thread overview]
Message-ID: <Zgak8uY-b1nC21-a@schatulle> (raw)
In-Reply-To: <ZgS04_VAp3iRNwlJ@irc-clt.no.swordarmor.fr>
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
Am Thu, Mar 28, 2024 at 01:08:03AM +0100 schrieb Alarig Le Lay:
> On Wed 27 Mar 2024 20:37:27 GMT, Frank Steinmetzger wrote:
> > +1 for Unison. I’ve been using it for many years now to synchronise between
> > the four PC systems in my household.
> >
> > Unison creates a local index of all files it syncronised. So when you move a
> > file around on one end, Unison will notice that because the file at the new
> > location has the same hash as the file at the old location. As a result, it
> > does not transmit the file anew to the remote host, but instead copies it
> > locally on the remote host.
> >
> > Since Unison uses ssh underneath, you can use ssh’s transparent compression
> > to speed up the transfer.
>
> I’ve been thinking about using it to synchronise dovecot maildir folders,
> since dsync is now deprecated. But I’m not sure about it as I never used
> it under “heavy” loads. Do you have any thoughts about it?
Among the many files I sync is my Mail folder. It currently contains around
106k files. My music collection is another 50k files. If there are no
changes and I did a recent run, then another run to look for changes takes
only very few seconds.
--
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.
A computer only crashes if your haven’t saved your text for a long time.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-29 11:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 18:58 [gentoo-user] How to synchronise between 2 locations J. Roeleveld
2024-03-27 19:08 ` Mark Knecht
2024-03-28 6:28 ` J. Roeleveld
2024-03-28 13:51 ` [gentoo-user] " Grant Edwards
2024-03-28 15:27 ` J. Roeleveld
2024-03-27 19:18 ` [gentoo-user] " ralfconn
2024-03-27 19:37 ` Frank Steinmetzger
2024-03-28 0:08 ` Alarig Le Lay
2024-03-29 11:24 ` Frank Steinmetzger [this message]
2024-03-28 6:30 ` J. Roeleveld
2024-03-28 16:33 ` ralfconn
2024-03-29 11:27 ` Frank Steinmetzger
2024-03-27 19:42 ` Matt Connell
2024-03-27 19:54 ` Frank Steinmetzger
2024-03-27 19:59 ` Matt Connell
2024-03-27 21:34 ` Frank Steinmetzger
2024-03-27 20:12 ` tastytea
2024-03-28 6:32 ` J. Roeleveld
2024-03-28 10:00 ` tastytea
2024-03-29 2:26 ` Grant Taylor
2024-03-29 11:32 ` Frank Steinmetzger
2024-03-29 13:32 ` J. Roeleveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zgak8uY-b1nC21-a@schatulle \
--to=warp_7@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox