Package Details: timeshift-systemd-timer 0.0.1-2

Git Clone URL: https://aur.archlinux.org/timeshift-systemd-timer.git (read-only, click to copy)
Package Base: timeshift-systemd-timer
Description: Add systemd support for timeshift
Upstream URL: None
Licenses: GPL3
Submitter: 1ridic
Maintainer: 1ridic
Last Packager: 1ridic
Votes: 5
Popularity: 0.51
First Submitted: 2022-09-05 04:53 (UTC)
Last Updated: 2022-11-23 03:31 (UTC)

Latest Comments

Managor commented on 2025-01-18 17:03 (UTC)

@mhussaincov93 The hourly service seems to just run timeshift --check --scripted every hour. The details on when new snapshots are created are still defined in timeshift itself. Say you want daily snapshots, just set daily snapshots in timeshift and enable timeshift-hourly.timer. The service simply check once per hour if it's time time to make a new snapshot.

m-danya commented on 2024-05-11 11:21 (UTC) (edited on 2024-05-11 11:22 (UTC) by m-danya)

@InvisibleRasta this package provides 2 pairs of systemd service and timer.

https://askubuntu.com/questions/1083537/how-do-i-properly-install-a-systemd-timer-and-service

You just need to enable one timer at your choice:

sudo systemctl daemon-reload
sudo systemctl enable timeshift-boot.timer # or timeshift-hourly.timer

Reboot your system, wait 10+delta minutes to let the timer trigger (OnBootSec=600 in /usr/lib/systemd/system/timeshift-boot.timer) and make sure that the backup is present in timeshift GUI

InvisibleRasta commented on 2024-03-19 23:30 (UTC)

how does this work?

mhussaincov93 commented on 2024-03-08 22:12 (UTC)

hi, could we have a timer for daily snapshots please? would be very, very greatful.

1ridic commented on 2022-11-23 03:36 (UTC)

You are right. I have modified the permissions, thanks thanks for reporting the bug！ @rab0171610

rab0171610 commented on 2022-11-21 11:47 (UTC)

Please feel free to correct me if I am wrong. Systemd entries in the journal show that the timeshift .service and .timer files are marked executable: " is marked executable. Please remove executable permission bits. Proceeding anyway." Maybe the correct permissions should be 644 in the PKGBUILD, not 755? It works either way, but 644 keeps these messages from appearing in the syslog.