Alexander Neumann

Hey, thanks for the suggestion. We don't have a clear concept for logging yet.

I'd like to defer the discussion until #1494 is done. I'm currently reworking the archiver code, which includes the reporting system for errors, status and totals. Let's come back to...

We're already creating a lock file in the repo for all operations, you've run into this in #708. A lock file is stored in the repo and contains some information...

@mlissner you could also just use the standard utility `flock` for this task, e.g.: ``` $ flock --nonblock --conflict-exit-code 0 /run/user/$UID/restic.lock restic backup [...] ``` It'll start restic once, and...

Sounds good, would you be interested to write some text for the manual? :)

I also don't like "advanced settings", however tempting that may be. I see you point @episource that there should be a way to either manually or automatically select the IO...

> Do you have any strong objections against adding a command line flag now? Yes: first we need to finish the new archiver code (see #1494), then we can tackle...

Thanks for taking the time to suggest this feature. I don't see that we have the resources to think about something so advanced as upgradable encryption (at least not short-...

Thanks for the detailed description of the use case. This could be achieved with a `copy` command discussed in #323.

You're right, that's not intuitive. We'll probably remove the "data processed bandwidth" eventually and replace it with a "backend read/write bandwidth" indicator. > Did restic help you or made you...