Alexander Neumann

> I just noticed that disk-full scenarios also returns with exit code 0, so the backup logs are a bit misleading on the final result. Hu, that shouldn't be the...

Nice, thanks for letting us know!

I've thought about this today, and I think we should improve the error handling: Restic should continue if possible (e.g. when just a single file could not be read), but...

Hey, thanks for raising this issue. The `--no-lock` option is only for supported operations, like `check`. Any operation that may add data (such as `backup`) does not support it, that's...

@gebi "it works" means restic does not return an error when you specify `--no-lock`, but for the `backup` operation it will still create a lock file. The `--no-lock` switch is...

I've decided to not add support for `--no-lock` for backup, at least not for now. If you want this behavior (and it feels to me you know what you're doing),...

@gebi I can understand your use case and what you're trying to do. In my opinion, just adding the small patch to allow `--no-lock` during backup has the potential to...

I assume you mean `restic backup --no-lock`? This would work for `backup`, but you'll end up with **many** lock files over time... For other operations (such as `snapshots`) changing the...

Hm. Maybe we can really do that: Not exit with an error if the lock file could not be removed. That'd work in most cases, especially in the ones you're...

Uh, that's not good, thanks for pointing it out again.