f5f386d297
This is to address a regression introduced in #131118. When syncing the first dataset, syncoid expects that the target dataset doesn't exist to have a clean slate to work with. So during runtime we'll check if the target dataset does exist and if it doesn't - delegate the permissions to the parent dataset instead. But then, on unallow, we do the unallow on both the target and the parent since the target dataset should have been created at this point, so the unallow can't know which dataset that got permissions just by which datasets exists. |
||
|---|---|---|
| .. | ||
| automysqlbackup.nix | ||
| bacula.nix | ||
| borgbackup.nix | ||
| borgbackup.xml | ||
| borgmatic.nix | ||
| btrbk.nix | ||
| duplicati.nix | ||
| duplicity.nix | ||
| mysql-backup.nix | ||
| postgresql-backup.nix | ||
| postgresql-wal-receiver.nix | ||
| restic-rest-server.nix | ||
| restic.nix | ||
| rsnapshot.nix | ||
| sanoid.nix | ||
| syncoid.nix | ||
| tarsnap.nix | ||
| tsm.nix | ||
| zfs-replication.nix | ||
| znapzend.nix | ||
| zrepl.nix | ||