Michael Gebetsroither

sure, np @chrisd8088 we might also want to add at least some kind of multiplexing to not need backwards incompatible changes in the future when more small helper cmds are...

added documentation about the cmdline oid lookup feature

@fd0 restic backup with --no-lock works here though and i'm deleting everything under /locks after a few hours automatically. ``` % myrestic check password is correct load indexes check all...

@fd0 The service account used by restic is simply not allowed to delete files on the GCS bucket. So a collision between those two commands is not possible. IMHO it...

@fd0 Any idea to my suggestion? If i understand the code correctly it would just be not creating any lock files and thus automatically a clean exit from restic (currently...

@ifedorenko yes, i've read the discussion, but as already mentioned there the `duplicacy` aproach needs an update to the repository format, this simple albeit not that fancy aproach does not...

@fd0 that's unfortunately as we really require the functionality for WORM backups (write once read many), and most backup users do so too, they just don't realize it, or only...

@fd0 hmm... the more i think about that the more i came to the conclusion that maybe we should just refuse to allow restic prune on such backends receiving snapshots...

@fd0 yea i meant `restic backup --no-lock`, yes many lock-files would be the outcome but they could either be deleted from the machine pruning the data or first check if...

Yea that would be awesome! btw... the current behaviour is a loop with error output where restic can't be killed normally but only with `kill -9` (for this case)