Hi,
I see this in the journal
May 09 14:36:06 f28h.local systemd-tmpfiles[3273]:
[/etc/tmpfiles.d/suspendfix.conf:7] Duplicate line for path
"/proc/acpi/wakeup", ignoring.
This file contains:
w /proc/acpi/wakeup - - - - PWRB
w /proc/acpi/wakeup - - - - XHC
They aren't really duplicate lines,
On Wed, 09 May 2018 at 16:46:09 +, john terragon wrote:
> I have the memory cgroup controller configured in the kernel. I want to use it
> myself directly without interference from systemd.
I don't think this is supported. systemd behaves as though cgroups v2 is
in use (single unified cgroup
On Wed, 2018-05-09 at 17:39 +0200, Michal Sekletar wrote:
> I was thinking that in addition to better log messages we could
> generate dot graph of the cycle and dump it to journal as a custom
> field. So people can then turn it into the picture and get a better
> understanding of the cycle. Do
Hi.
I have the memory cgroup controller configured in the kernel. I want to use it
myself directly without interference from systemd. I tried setting
DefaultMemoryAccounting=no in system.conf but systemd seems to still interfere
with the hierarchy for the memory controller (e.g. systemctl
On Fri, Apr 27, 2018 at 6:01 AM, Andrei Borzenkov wrote:
> апр 27 06:54:14 bor-Latitude-E5450 systemd[1582]: foo.service: Found
> ordering cycle on foo.service/start
> апр 27 06:54:14 bor-Latitude-E5450 systemd[1582]: foo.service: Found
> dependency on bar.service/start
>
On Tue, May 08, 2018 at 01:34:58PM -0500, Thad Phetteplace wrote:
> Hi systemd developers,
>
> I'm wondering what the state of development is on the d-bus interface
> for systemd-networkd. Currently the interface appears to be minimal,
> but I've also seen comments that a full featured API is