aawsome
aawsome
@Chostakovitch You can try to run a `rustic check --no-cache` to see if there are problems in the repository while not using any cache. If there are no warnings without...
Hi @catap Can you describe what's the issue for your? I can use `rustic webdav` in combination with `cadaver` without any problem on my laptop (Just tried it out)....
About lftp: Yes, seems like `HEAD` is not supported on dirs. I am no specialist in the webdav protocol, but `dav-server` (the crate we use) claims in https://github.com/messense/dav-server-rs that it...
Hi @benjaminweb, thanks for opening this issue! I can understand your desire, but I must say there are some major difficulties here: - by design, the `backup` command is designed...
Hi @Chostakovitch I fully agree about `RUSTIC_COMMAND`. - `RUSTIC_HOOK_COMMAND`: IMO the command should be able to do this by itself using `$0` or equivalent. - `RUSTIC_FAILED_COMMAND`: I think this will...
> Hey [@aawsome](https://github.com/aawsome), what do you think about keeping `RUSTIC_COMMAND` as you suggested and adding `RUSTIC_PROFILE`, so hooks can be factorized, and forget about my other suggestions which are too...
duplicate of https://github.com/rustic-rs/rustic_core/issues/22 Actually I cannot yet explain why this is happening. But I can confirm that I also had left-over `rclone` instances. But it seem I'm not having them...
Actually, I thought that when the rclone backend is dropped, it will always call a `kill` on the created subprocess. Technically the `Child` process is wrapped in an `Arc` and...
I did some other tests and can say that I can reproduce the behavior when I manually run `rustic check`. Now I'll try if #73 fixed that...
Unfortunately, #73 didn't fix it.. I'll have to take a deeper look into where things could go wrong...