[Users] Zimbra OpenPGP Zimlet 2.5.1

[Barry De Graaff]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

While one can flush *some* cache with `zmprov fc all`, this will NOT apply to updates
in translations... that is why the mailboxd restart is needed sometimes.

I don't think it can be avoided, so we will need to find something that makes
it a once-in-a-transaction  operation.

Kind regards,

Barry de Graaff
Zeta Alliance Founder
www.zetalliance.org

Skype: barrydegraaff.tk
Fingerprint: 9e0e165f06b365ee1e47683e20f37303c20703f8

 - ----- Original Message -----
From: "David Sommerseth" <dazo at eurephia.org>
To: "Barry De Graaff" <barrydg at zetalliance.org>, "Truong Anh Tuan" <tuanta at iwayvietnam.com>
Cc: users at lists.zetalliance.org
Sent: Thursday, May 26, 2016 2:55:33 PM
Subject: Re: [Users] Zimbra OpenPGP Zimlet 2.5.1

 - -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 26/05/16 14:46, Barry De Graaff wrote:
> Some Zimlets require a zmmailboxd restart, the question is, how to
> deal with 10 zimlets that require a zmmailboxd restart.
>
> With the current setup, that would be 10 restarts, on every
> upgrade, and that is not funny.

Yupp!

I don't remember now if there are some triggers you can activate at
the end of a transaction.  If it exists, then it would be a restart
per yum execution.

But this sounds more like a hack to me.  It just as well points out
something which ideally should be handled far more gracefully
internally in the mailboxd service.  Perhaps coupled with a "flush
zimlet" operation?


 - - --
kind regards,

David Sommerseth
 - -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJXRvJFAAoJEIh23YAzae8U4M8QAIkORGmLeqMuJ6bbUbkurkaC
f5QvRF0o9IdUfT5SsRqe075O9PED3uF0W8luNxhHq8SsB269WJ81LjSR6UtybU9P
FsgI3ipTYoMsaXs7oZHbYBZm99lXvrEMSybuLV7YzkrPJ5X1lZ0T6QhG0P23ebl3
79RLMWiHsu/JhIlfBxdOgsvZ4pV9d3KeIfO1DNAnZIQSwOi2mYZIj9ftLnw4ILZE
K5FBiGkAczngLJt6rum3EtFDm031hCr+OnrV47Bj4dfZ/RwkgQReOMVw6ZTm1UXy
Sw/+aF0kQaoRkgwCs3LnGdJOfoCMXHc5Vpo0dS+Xp9oEuhk37tWuga88RAATIQKK
vxRfm74JXq0bIimFiiHiTOT+RM7jDl2TfMdo4oKl++POo9xX4G4Akm5+60sIx11w
fEWVhZST4yubINp2/TX5BNow/WTaGFP1k8AaaAVUavO3qWh8ehRL5IizGoKBhvjb
9OJBUbpS9JyZUiT9kSAnLT6UzxPjgvAdqbGjZHQ3+2I2V7QzsCsr3SjgfKls5p9r
B0872OdocrcX3KN1lY0HwvrSBE1K+Cge+CJZa8uAH882jQu+q3ezmIUrTZnoRwzz
pd/LPY0RCaMYF1fLVZKBClkdmsQEwUHWrxAQRa08TAaEIa2b/7celjAxX1is5EhM
10mwakcsCB1b/a2pdgzc
=N3eJ
 - -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: OpenPGP.js v2.3.0
Comment: http://openpgpjs.org

wsFcBAEBCAAQBQJXRvMpCRAg83MDwgcD+AAAdaoQALc2PONsTD40k/Mmqi8W
zhDE0ou6Y/zGWIJHhNajdinJFNpNfrTeXGKiZS9QOa5e7JzOIbbru13SLai4
FxJP4vONRiNgCecvwoxdDV+zY0CNFgw3hf96yD4pbFHddmbn5XwA5IyqqXuq
JEnuS2zOqvjRr8J1Dg8/Ca3g+JmYOectSv7EED2tzLWw3dZl1E2IrxSC5H9G
tGwXU5V+Kl77uZxDmtGTgJZi8eUuXlHTkq6K4TWoKshtwtlR/GcUphHi/DzV
lDAGP+6ooruuCGwfkyGL/2dPwOoe/RStvqzclUNSN0ODdLPpdgknY3ocTo3E
l5vUOYpTOT7WFTw5wZ+rfJH+d84grSkBp6Xj8WdBJA7WTvo4jnbW4eFh1TS1
07CT5navec8uYZxnjyxj70PeAAKmBR0G5pIUjr4dmdOJ2I4FviJ5rVoEpAzg
FV7ZQyLujyfyzXEB8bv3VDTlvWJJuB2pF3f38gb8Ow2OUuoZlcX7bjhd+0S+
5rjn14rAo935QV4E3KDNeKbjc6G7TooLVmwT6vOOSMx4bRYEW8Pa2RTay1gX
8o+9oFmcX7emCplJOU274qwxp5ba9aCI9P02UQALZDr+C9HkadPtIHRrJUBm
hdOikXUeczfUX8idyRhZsJDppH0BVC/vWA16wdVBKd8cLyX8TrwEh1RodeSg
6VsM
=oL2n
-----END PGP SIGNATURE-----