4 ms·

Seconding obnam. Speed it up with: lru-size=1024 upload-queue-size=512 See http://listmaster.pepperfish.net/pipermail/obnam-support-obnam.org/2014-June/00308

• drKarl 12y ago
  Thanks, added this info to the list
• hsivonen 12y ago
  Using /dev/urandom instead of /dev/random help, too. http://listmaster.pepperfish.net/pipermail/obnam-support-obnam.org/2015-February/003421.html http://listmaster.pepperfish.net/pipermail/obnam-support-obn...
  • feld 12y ago
    This makes me highly suspect about the encryption implementation of obnam.
    • joeyh 12y ago
      Obnam uses gpg for encryption. The only novel thing is its use of symmetric encryption keys which are used to encrypt the data and are included in the backup repository, encrypted by your regular private gpg key. This allows giving additional gpg keys access to the backup after it has been made. http://liw.fi/obnam/encryption/ http://liw.fi/obnam/encryption/ (Which is useful for eg, backing up a server. You can make a dedicated gpg key for that server, but give your personal gpg key access to the backups to restore later.) Anyway, the generation of the symmetric encryption key is what needs an entropy source. AFAIK this is done once per repository.
      • feld 12y ago
        Yes I see this now. It wasn't as obvious at first glance. However, I'm surprised this issue with random wasn't caught much, much sooner.