On Sat, Aug 20, 2016 at 11:53 PM, Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> On Sat, Aug 20, 2016 at 11:01:07PM -0400, Che wrote:
> > From GitHub:
> >
> > "Support for snapshots has been removed."
>
> See //github.com/systemd/systemd/commit/36b4a7ba55.
>
> Zbyszek
>
Well, that make
On Sat, Aug 20, 2016 at 11:01:07PM -0400, Che wrote:
> From GitHub:
>
> "Support for snapshots has been removed."
See //github.com/systemd/systemd/commit/36b4a7ba55.
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lis
>From GitHub:
"Support for snapshots has been removed."
Has the back-story here been endlessly covered, here and elsewhere,
previously? And if so -- where would be the best place to read up on
understanding why it's no longer around in systemd..? Or perhaps someone
here will explain. Again, if ne
When I issue sysrq+t I'm getting a lot of "missed kernel messages"
messages in the journal. Are there really hundreds of messages
missing? Is this expected? I could increase the kernel message buffer
to 1M and see if they're really missing I guess; the sysrq+t output is
too big to fit by default an
On Fri, Aug 19, 2016 at 11:03 AM, Lennart Poettering wrote:
... However, systemd
> does not support natively to stop services by timer, currently. This
> means for the "systemctl stop" part you always have to explicitly
> invoke it.
Does it make sense to implement this as a feature? And if so,
