Issue was rised in this thread:
https://mailman.archlinux.org/pipermail/arch-general/2014-May/036162.html
Disclaimer:
I almost have no expereince in C.
So this patch can contain some silly mistakes. But it 'works for me'.
Please consider it as RFC.
-8---
Cron-like timers are useful for
On Sun, May 11, 2014 at 07:53:55PM +0400, Alexander Bashmakov wrote:
Issue was rised in this thread:
https://mailman.archlinux.org/pipermail/arch-general/2014-May/036162.html
Disclaimer:
I almost have no expereince in C.
So this patch can contain some silly mistakes. But it 'works for me'.
2014-05-11 20:09 GMT+04:00 Dave Reisner d...@falconindy.com:
On Sun, May 11, 2014 at 07:53:55PM +0400, Alexander Bashmakov wrote:
Issue was rised in this thread:
https://mailman.archlinux.org/pipermail/arch-general/2014-May/036162.html
Disclaimer:
I almost have no expereince in C.
So this
Fedora Rawhide (systemd-212) vs Fedora 20 (systemd-209) and a Btrfs degraded
boot.
With Fedora 20, at basic.target, I get the cylon eye A start job is runing for
dev-disk-by….. which eventually fails and I get a dracut prompt, and a note
about the sos report. Great. That's what I need to find
It looks like --list-boots is broken. I have have the same problem on Rawhide
with systemd-212-4.fc21.x86_64, which is a completely different VM. Here are
the last three items with --list-boots
-2 95117f702e4d43619072f87b20b2f31b Sat 2014-05-03 20:38:22 MDT—Sat
2014-05-03 20:47:17 MDT
On Sun, May 11, 2014 at 9:30 AM, Alex B pkunk...@gmail.com wrote:
It's ok for one timer, but not for the set of them.
In general I'm want to schedule all maintenance tasks to 5 a.m.
or lunch break and forget about them.
This applies both for distro provided timers an my own.
I'd personally
