Follow-up Comment #4, bug #25455 (project duplicity): I ran into this problem too with duplicity 0.5.16. 40 or more gpg processes are started, and it OOMed my machine.
I filed a bug here about it: <http://bugs.debian.org/531786> The problem is that get_fileobjs is used to generate a list of open file objects for each manifest file, and these are GPGFile objects that are each backed by one gpg process that runs as long as they are open. So the excessive gpgs occur at the start of the incremental backup, when it's examining what was backed up before. Once it starts adding to the backup, only 2 gpgs are running at a time. I have some other things to say in the Debian bug about possible approaches to fix it and why big lists of open FDs is not a good idea. Joey Hess <[email protected]> _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?25455> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/ _______________________________________________ Duplicity-tracker mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/duplicity-tracker
