duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Fwd: GPG taking many ressources


From: Kenneth Loafman
Subject: Re: [Duplicity-talk] Fwd: GPG taking many ressources
Date: Sat, 14 Aug 2010 14:32:47 -0500
User-agent: Thunderbird 2.0.0.24 (X11/20100411)

Henrik Olsen wrote:
> On Aug 12, 2010, at 2:02 PM, address@hidden wrote:
> 
>> On 12.08.2010 13:21, Kenneth Loafman wrote:
>>> Jacob Godserv wrote:
>>>> On Tue, Aug 10, 2010 at 17:25, Henrik
>>>> Olsen<address@hidden>  wrote:
>>>>> As I'm still having the issue, I was wondering if GPG 1.4.10
>>>>> could be the issue, and I should try 2.x instead?
>>> There are still some interface changes that need to be made for
>>> 2.x, but it might work.
>> I recall having used duplicity together with gpg2 flawlessly.
>> Worked for me.
> 
> Trying with gpg2 now. Took a bit to get it to compile with the many
> dependencies, but now duplicity can use it, as long as I change
> self.call from gpg to gpg2 in GnuPGInterface.py.
> 
> But... Unfortunately I still see a heavy ressource usage, exactly
> like with gpg. Now with gpg2 as well, and as I noticed yesterday with
> gpg, also even if only one process is running:
> 
> ps aux | grep gpg root     98278  95.1  0.0  2436668    804 s000  RN+
> 8:42PM   2:28.35 gpg2 --status-fd 5 --passphrase-fd 10 --logger-fd 3
> --batch --no-tty --no-secmem-warning --decrypt holsen   98287   0.8
> 0.0  2435036    528 s002  S+    8:44PM   0:00.00 grep gpg
> 
> On non-OSX usage, do anyone ever see gpg usage like this?

Did gpg2 solve the issue of multiple gpg processes running?  From your
example, it looks like it did.  If so, that was the issue that I was
trying to solve.  Every gpg process that is still open is tying up 3
file descriptors and a very small amount of memory, but no CPU.  With
long chains of incrementals some people were running out of open files.

...Ken


Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]