You probably want to increase that. It's an extremely low limit.
Search for "ubuntu increase max files limit" and you will find answers.
Don't be miserly, set it at 32K or 64K.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity
ulimit -n -> 1024 (default install)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1727653
Title:
duplicity fails with unknown error
Status in duplicity package in Ubuntu:
In
How many open files allowed ("ulimit -n")? Other than memory, "too many
open files" has been the culprit that keeps fork from working.
On Sat, Oct 28, 2017 at 1:10 PM, Wolf Rogner wrote:
> Please read my comment again:
>
> Only when autostarted the error occurs. When launched
Please read my comment again:
Only when autostarted the error occurs. When launched manually (the
memory situation is the same) it works.
And: I have 16 GB RAM on this machine. I think there will be some
contiguous memory available.
--
You received this bug notification because you are a
The first launch after a reboot is one where the memory is less
fragmented, and possibly where other tasks have not started, so clean
memory access is most likely. The current manifest file reader takes in
the full file at one time and breaks it apart in memory. This worked
well when there was
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
I doubt this being a duplicate:
The error message differs and it only happens when deja-dup starts
automatically.
When launched manually, deja-dup and duplicity work fine.
Currently only the first
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
** This bug has been marked a duplicate of bug 1720159
Cannot allocate memory with large manifest file since 0.7.03
--
You received this bug notification because you are a member of Desktop
Packages,
7 matches
Mail list logo