Did you `systemctl enable rsync-Saruman.timer` to activate the timer?
Timers can be enabled and disabled just like services, you need to enable
it after creating.
- Dave
On Fri, Aug 30, 2019 at 8:05 PM Kenneth Porter
wrote:
> I've created my service timer with the following:
>
> [Timer]
> #
I've created my service timer with the following:
[Timer]
# wait a bit after boot to let our victim catch up with its work
OnBoot=13m
# let the victim get some work done between backups
# we use inactive to prevent back-to-back backups if they run long
OnUnitInactiveSec=1h
I then run
I have a backup script that runs periodically via cron. Instead of mailing
me a large log, I wanted to have it append to a log file that can be
rotated and compressed by logrotate. So I removed my link from
/etc/cron.hourly and created service and timer units.
My first cut at writing a log
On Sat, 31 Aug 2019, Daniel Otero Oubiña wrote:
> I forgot to say that the devices on crypttab are also configured with
> `noauto`, that's why I was adding the dependences manually.
Even with `noauto`, the manual dependency isn't needed. The dependencies I
described were all about the block
I forgot to say that the devices on crypttab are also configured with
`noauto`, that's why I was adding the dependences manually.
The strange behavior for me is that, if I do not put the `x-systemd.automount`
everything works fine: the devices are not decrypted until I try to mount
the final
On Fri, Aug 30, 2019 at 04:08:39PM +0200, Hans de Goede wrote:
> Hi All,
>
> I already filed a github issue for $subject:
> https://github.com/systemd/systemd/issues/13437
>
> But I'm not sure how close github issues are watched hence this email. It
> would be nice if we can get this fixed for
Hi All,
I already filed a github issue for $subject:
https://github.com/systemd/systemd/issues/13437
But I'm not sure how close github issues are watched hence this email. It would
be nice if we can get this fixed for F31 beta, or if some more time is needed,
at least get this regression
Hi,
I found when we set CPUAffinity in unit file or property by DBUS we need
to restart daemon. It's strange because CPUShares could be applied w/o
restarting daemon. So after systemctl set-property my-slice CPUShares=50
I see changes in cgroup fs immediately, but CPUAffinity is not in the
On Fri, 30 Aug 2019, Daniel Otero Oubiña wrote:
> Hi all!
>
> I have found a somehow strange systemd "feature" that I'm not sure if it's
> a bug. Let me know if you prefer having this reported on GitHub instead.
>
> First, let me explain my setup: I have a data filesystem that is split in
> two
