rzerres/dsnap-sync
1
0
Fork 0
Code Issues Pull Requests Releases 1 Activity

remove systemd service

Browse Source
This commit is contained in:
James Barnett
2017-11-11 12:59:03 -05:00
parent 52db8f099a
commit 38caa9cefa
3 changed files with 0 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@@ -59,22 +59,6 @@ The first time you run `snap-sync` for a particular disk (new UUID) you will be
prompted to choose a backup location on that disk. If the directory you specify prompted to choose a backup location on that disk. If the directory you specify
does not exist, it will be created. does not exist, it will be created.
## Systemd unit and timer
A systemd unit and timer are included. These are instantiated units. You need to
specify the UUID of the disk to back up to in the `systemctl` call. Note, once
again, the disk **must** be mounted, and it **must** only be mounted in one
place. Example:
# systemctl start snap-sync@7360922b-c916-4d9f-a670-67fe0b91143c
The timer included is weekly. Edit both files to your taste.
You can exclude a configuration from backup by setting `SNAP_SYNC_EXCLUDE=yes`
in your snapper configuration file. Additionally you should run snap-sync at
least once for a new disk without using the service so you can be prompted for
the backup location.
## Example command line usage ## Example command line usage
### No arguments ### No arguments

9
systemd/snap-sync@.service
View File

@@ -1,9 +0,0 @@
[Unit]
Description=Run snap-sync backup (UUID: %i)
[Install]
WantedBy=multi-user.target
[Service]
Type=simple
ExecStart=/usr/bin/snap-sync --UUID %i --noconfirm

10
systemd/snap-sync@.timer
View File

@@ -1,10 +0,0 @@
[Unit]
Description=Run snap-sync weekly (UUID %i)
[Timer]
OnCalendar=weekly
AccuracySec=12h
Persistent=true
[Install]
WantedBy=timers.target