[This comment was seemingly hidden?]
> The real question is, why is "[ $(date +\%w) -eq 0 ]" in there, when
cron can do day-of-week like:
>
> 24 0 8-14 * 0 root [ -x /usr/lib/zfs-linux/scrub ] && /usr/lib/zfs-
linux/scrub
This is because if you specify the "day of month" and the "day of week"
The real question is, why is "[ $(date +\%w) -eq 0 ]" in there, when
cron can do day-of-week like:
24 0 8-14 * 0 root [ -x /usr/lib/zfs-linux/scrub ] && /usr/lib/zfs-
linux/scrub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
zfs-linux (0.6.5.6-2) unstable; urgency=medium
...
* Scrub all healthy pools monthly from Richard Laager
So Debian stretch, but not Ubuntu 16.04.
Deleting the file should be safe, as dpkg should retain that. It sounds
like you never deleted it, as you didn’t have it before this upgrade. So
it
@rlaager ref for "long time ago"? (Looking for release notes and
specific version)
I've been reasonably diligent in monitoring my pool scrub activity, I
would "guess" that maybe in the last 2-3 months I may have lost track.
But also I only upgraded from Ubuntu 16.04 LTS sometime late-2019 Fall
This was added a LONG time ago. The interesting question here is: if you
previously deleted it, why did it come back? Had you deleted it though?
It sounds like you weren’t aware of this file.
You might want to edit it in place, even just to comment out the job.
That would force dpkg to give you a
