On Wed, Jul 25, 2018 at 5:25 AM George Xie <george...@gmail.com> wrote: > > thanks for your reply. > > odds enough, on both aforementioned boxes, MemoryAccounting is set to no:
There is probably some other service that had MemoryAccounting=yes which in turn effectively (even though dbus property doesn't reflect that) enabled MemoryAccounting on all "sibling" services. > the good news is, after setting `DefaultMemoryAccounting=yes` in > /etc/systemd/system.conf, and a `systemctl daemon-reexec`, all units have > correct memory usage info. Tasks and memory accounting is now enabled by default in upstream so I figure these weird issues are more visible on CentOS where accounting still defaults to "no". Michal _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
