Hi,

since I prefer systemd-timers over cron jobs (systemctl list-timers is great and
they log automatically to journalctl), I created a service and a timer for it. 
I have no
idea what would be the best way to create a pull-request for them, so I post
them here:

When you create them yourself you can put them in /etc/systemd/system

qubes-sync-clock.service
[Unit]
Description=This syncs the clock

[Service]
type=simpel
ExecStart=/usr/bin/qvm-sync-clock

[Install]
WantedBy=default.target


qubes-sync-clock.timer
[Unit]
Description=Sync the clock every 6 minutes

[Timer]
Persistent=false
OnBootSec=15
OnCalendar=*:0/6
Unit=qubes-sync-clock.service

[Install]
WantedBy=timers.target

When you have both files:
systemctl start qubes-sync-clock.service
systemctl enable qubes-sync-clock.service
systemctl start qubes-sync-clock.timer
systemctl enable qubes-sync-clock.timer

When you want to see when the timer ran the last time and will run the next
time:
systemctl list-timers

And when there is something to log, it is in the journal (journalctl)

The interesting man-pages:
* systemd.timer(5)
* systemd.time(7)

I have not that much experience with services/timers, so I just adapted what I
use for my personal timers…

Niels

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/87y450ygky.fsf%40mailbox.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to