From: Amadeusz =?utf-8?B?xbtvxYJub3dza2k=?= <aidecoe@aidecoe.name>
To: David Mazieres expires 2015-11-21 PST
 <mazieres-f72cdtyxmh2n26c2fbep99wgpw@temporary-address.scs.stanford.edu>
Subject: Re: muchsync files renames
In-Reply-To: <87oahxojlv.fsf@ta.scs.stanford.edu>
References: <878u93ujdo.fsf@freja.aidecoe.name>
 <876146o920.fsf@ta.scs.stanford.edu> <871teu8kdd.fsf@freja.aidecoe.name>
 <87oahxojlv.fsf@ta.scs.stanford.edu>
User-Agent: Notmuch/0.20.2 (http://notmuchmail.org) Emacs/24.5.1
 (x86_64-pc-linux-gnu)
Date: Wed, 26 Aug 2015 07:31:34 +0100
Message-ID: <87y4gyftmh.fsf@freja.aidecoe.name>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
 micalg=pgp-sha512; protocol="application/pgp-signature"
Cc: notmuch@notmuchmail.org
Precedence: list

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi David,

(Resending, because I forgot to Cc mailing list.)

David Mazieres <dm-list-email-notmuch@scs.stanford.edu> writes:
>> 3. I run muchsync SERVER.
>> 4. When it lasted much longer then initialization I canceled it by
>> single SIGINT (^c).
>
> Interesting.  I wish I knew why this was taking much longer than running
> it on the server, and whether the delay was caused by client activity or
> server activity.

I think there was something happening on server side because with --noup
it has been completed in few seconds.

 > I don't suppose you'd be willing to make a copy of your mail database
 > to repeat the experiment without any risk of messing up your real
 > maildir?

I would try it, but unfortunately I would have to make a bit more space
for having second copy of my mail.  I am testing muchsync on the same
machine between different users home directories, so it already takes
some space.  I'll try the experiment some day this week, I hope.

>> 5. I rerun muchsync SERVER and then it notified me that notmuch
>> identified files names changes - more than 1000.
>
> Were the link changes on the client (sent) or the server (received)
> side?

On the server side.  That's why I am worried.


> I don't think that will change things.  maildir.synchronized_flags
> will make things slower, but it shouldn't affect the SUMMARY numbers
> you see at the end of muchsync, other than maybe files moving from
> .../new to .../cur.  But presumably most of your mail files were
> already in cur directories.

So what would happen on my machine is that first client initialization
took place.  During this stage muchsync moved some files from new/ to
cur/. Later running "muchsync SERVER" tried to reflect client changes on
server by pushing renames requests to server.  Is it what actually could
happend?


=2D-=20
Amadeusz =C5=BBo=C5=82nowski

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1

iQJ8BAEBCgBmBQJV3V1HXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCMzcyRTFENjI5NUM1MzYwQTQwODQyRUZD
QkNDODAyM0Y1OUUxNzA0AAoJEMvMgCP1nhcE8u8P/jKjYUg1yhZSps+PPQB8BSnY
REdm/QK/CHsmGnY5jAa1OvoAHK23hh1xxeb+4H88AqygGE/1LpPZVm3caBaj4a97
QwOWrB1vPMfor38ZVw8oPOYT0hwSgpazYOSMp3biDE7wxnh0e5zVxq1AOratgvR7
Viaqdjc/c+AtfvFemSip2voxT5kbuJbjPKN4Ai2+FBIh3swgfa14UpphWm2Wa94r
hseBA/gqCAiGAH8y3CRUPkQAxctg0T7sWSybBRU+1puHLAvRrkNkXDSj/5TTvbKq
rmGW9CrpxPBOA3g4QzS8cs22cpQ6pDqr2hWUzKgb+vYmzWBUM/f1PvXin/IC4bCT
T3lixs1t7vvcPl7EPGiVGe6d+c1xdSnCriHsMJSwfTDwT95o/bm0kK3WDXNElt3M
QvrE5j20ZYP4KrNjNBJrCOBetXOgIdgzLmTYAoJMw72lCCRqtf+f3A42MUf/HPNC
qz/6wQrrN7DN4UcAziWcpmY7P+C+RJ5vrKirq+mxwKlpy78ceu64Jz8918L182yH
pLVOPzKjvIdiQ57Xi5VP32AzYogEFmpI4dNe4rcVGuUwY7f01+lqhgZUDi2rH0Tn
ObbFW+KWtL3ysEpgDFKFY5MUJ++FzmjM+RUOHfS+pXkVSvChBDr0lV5sbDUY08X+
OfmYyT6a4ZSIt0nEc2fB
=zaT+
-----END PGP SIGNATURE-----
--=-=-=--