Ignore error for disappeared source files

[kalos]

There is a way, in resticprofile or systemd service, to disable error on "Warning: failed to read all source data during backup"
restic/restic#3098
My systemd service is:

[Service]
Type=notify
Restart=no
WorkingDirectory=/home/kalos/.config/resticprofile
Environment="HOME=/home/kalos"
ExecStart=/usr/local/bin/resticprofile --no-prio --no-ansi --config profiles.yaml --name all-my-backups backup

Thanks.

[creativeprojects]

Yes I can see how it would be an interesting feature.
The main problem is to detect this particular error:

• restic does not return different codes, it's one code for all errors and another when you stop the process (^C): Return different exit codes for different failures restic/restic#956
• I can pipe the output to analyse it, that is something I started to do for the status file and I suppose I could try to detect it there. I need a bit more testing for that

[creativeprojects]

No actually I was wrong, there's a different exit status 3 when a snapshot was created but some files were missing: https://restic.readthedocs.io/en/latest/040_backup.html#exit-status-codes 👍🏻

[kalos]

Sorry, maybe I haven't been exhaustive.

Since restic has a specific exit code, I think it's not very difficult to implement a check on it.
For this, I was asking you if you could get around the problem by working on the systemd service.

ps: Thank you so much for this very complete restic wrapper!

[creativeprojects]

Yes, considering restic is returning an exit code 3, it's easy to ignore it and make resticprofile return with a code 0 (telling systemd all was fine).

I'll add a parameter in the configuration for that though, I don't want to change the default behaviour 👍🏻

[creativeprojects]

It will be available in the next release (0.13.0)

https://github.com/creativeprojects/resticprofile#warnings-from-restic