Doc: Update mount example to work on more systems (#147)
`0 */1 * * * if [[ -d /mnt/backup ]]; then rsync_tmbackup.sh /home /mnt/backup; fi` this is not valid for all sistems. Is not POSIX compilant. IMHO best soltuion is `if grep -qs /mnt/backup /proc/mounts; then rsync_tmbackup.sh /home /mnt/backup; fi` Best regards and thanks for your script.
This commit is contained in:
committed by
Laurent Cozic
parent
e2b4148855
commit
a9eb0efbad
@@ -68,6 +68,8 @@ On macOS, it has a few disadvantages compared to Time Machine - in particular it
|
|||||||
|
|
||||||
0 */1 * * * if [[ -d /mnt/backup ]]; then rsync_tmbackup.sh /home /mnt/backup; fi
|
0 */1 * * * if [[ -d /mnt/backup ]]; then rsync_tmbackup.sh /home /mnt/backup; fi
|
||||||
|
|
||||||
|
0 */1 * * * if grep -qs /mnt/backup /proc/mounts; then rsync_tmbackup.sh /home /mnt/backup; fi
|
||||||
|
|
||||||
## Backup expiration logic
|
## Backup expiration logic
|
||||||
|
|
||||||
Backup sets are automatically deleted following a simple expiration strategy defined with the `--strategy` flag. This strategy is a series of time intervals with each item being defined as `x:y`, which means "after x days, keep one backup every y days". The default strategy is `1:1 30:7 365:30`, which means:
|
Backup sets are automatically deleted following a simple expiration strategy defined with the `--strategy` flag. This strategy is a series of time intervals with each item being defined as `x:y`, which means "after x days, keep one backup every y days". The default strategy is `1:1 30:7 365:30`, which means:
|
||||||
|
|||||||
Reference in New Issue
Block a user