On Fr, 23.11.18 12:48, Piotr Dobrogost ([email protected]) wrote:
> I enabled unified hierarchy by passing "systemd.unified_cgroup_hierarchy"
> kernel parameter and `stat -fc %T /sys/fs/cgroup/` reports "cgroups2fs" yet
> the memory limit set by `systemd-run --user -p MemoryMax=100M
> /usr/bin/
Am 23.11.18 um 14:03 schrieb deepan muthusamy:
> If I start my application manually, CPU consumption is less than 2%.
> If I start same application as system service, CPU consumption is more
> than 100%.
>
> There is no cout statements in my application.
>
> I tried to start under a */screen/*
If I start my application manually, CPU consumption is less than 2%.
If I start same application as system service, CPU consumption is more than
100%.
There is no cout statements in my application.
I tried to start under a *screen* as system service. This time consumption
has reduced little bit.
I enabled unified hierarchy by passing "systemd.unified_cgroup_hierarchy"
kernel parameter and `stat -fc %T /sys/fs/cgroup/` reports "cgroups2fs" yet
the memory limit set by `systemd-run --user -p MemoryMax=100M
/usr/bin/krusader` doesn't work as `cat /proc/$(pidof krusader)/status |
grep VmRSS` re
On Do, 22.11.18 19:57, Eberhard Stoll ([email protected]) wrote:
> > It could be that they remain mounted within another mount namespace. You
> > don't have any weird udev rules which call `mount`, do you?
> >
> > If you have a recent util-linux, run `sudo lsns -t mnt` to see live
> > namespaces. For
