Lyonel Vincent

This should be compatible with the `direnv` tool (which does exactly this). cf. https://direnv.net/

I've prefixed all calls to `snebu` with `time` on all my clients and backup server to get a baseline and tomorrow I will switch to a `cleanup` version to measure...

It looks OK so far, I've replaced the snebu binary by one from the `cleanup` branch. I've had to manually create the `log` table, though (`snebu expire` was complaining). I'll...

The new version indeed shows an improvement in speed (backup times): machine2: New version | Old version ------------ | ------------- real 13m44.315s | real 21m12.750s user 3m23.057s | user 3m54.784s...

These are incremental backups of existing hosts, I've e-mailed you the link to my dashboard (where you can see the `log` entries).

The `.nobackup` is probably easier to implement (filtering out sub-trees in `snebu-client` is indeed a few command away). AFAIK GNU `tar` doesn't honour `nodump`, but BSD `tar` and Star do...

Sounds good, having such `-nodump` predicate in `find` will definitely be beneficial to everybody. In the meantime, `.nobackup` can be a valid option (and usable even on `nodump`-incompatible filesystems)....