To edit the timer setting, you can use
$systemctl edit raid-check.timer
Then add
[Timer]
OnCalender=
OnCalender=Mon *-*-1..7 1:00:00
Between the comment. Replace the content after the second OnCalender
Git Clone URL: | https://aur.archlinux.org/raid-check-systemd.git (read-only, click to copy) |
---|---|
Package Base: | raid-check-systemd |
Description: | Raid data scrubbing script with systemd timer to be used with mdadm. |
Upstream URL: | https://wiki.archlinux.org/index.php/RAID#Scrubbing |
Keywords: | mdadm raid scrub systemd |
Licenses: | |
Conflicts: | |
Submitter: | TheChickenMan |
Maintainer: | GI_Jack |
Last Packager: | GI_Jack |
Votes: | 10 |
Popularity: | 0.158223 |
First Submitted: | 2016-06-07 08:44 |
Last Updated: | 2020-12-20 10:19 |
To edit the timer setting, you can use
$systemctl edit raid-check.timer
Then add
[Timer]
OnCalender=
OnCalender=Mon *-*-1..7 1:00:00
Between the comment. Replace the content after the second OnCalender
It looks like this is still out of date. You get the following when trying to build:
==> Making package: raid-check-systemd 4.1-2 (Sat 20 Jun 2020 10:42:37 PM)
==> Retrieving sources...
-> Downloading mdadm-4.1-1.el7.x86_64.rpm...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
==> ERROR: Failure while downloading http://mirror.centos.org/centos/7/os/x86_64/Packages/mdadm-4.1-1.el7.x86_64.rpm
Aborting...
Error downloading sources: raid-check-systemd
Thanks for the heads-up. You could use the "flag as out of date" button next time also. It's hard to notice when something goes out of date when I'm not looking to reinstall it regularly. It should be all set now.
This is currently broken. The centos package needs a version bump:
_cent_rel=13
sha256sum='f4ba05c4a966ebfa90dc510cf4d67187dbd3666a50d2bd96942dfd3e57f89704'
Should be fixed now. Wish there was an easier way to know when the source for this stuff gets updated other than it not working for someone.
Gah, I've been all over the place with this one. Glad to see you're up as early as I am :). Thanks for getting on this.
Looks like they updated their source to
mdadm-4.0-5.el7.x86_64.rpm
You are supposed to use:
$ sudo systemctl enable raid-check.timer
I have that problem:
systemctl enable /usr/lib/systemd/system/raid-check.service
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
Yes, it does say "started" again even though it's actually finished.
Pinned Comments
TheChickenMan commented on 2017-04-30 19:00
You can view the status of the service while it is running in the kernel log with dmesg. You can also review status with the following:
$ systemctl status raid-check.service
$ systemctl status raid-check.timer
$ systemctl list-timers --all