Re: [systemd-devel] systemctl show outputs incorrect MemoryCurrent value

2018-07-25 Thread George Xie
> dealing internally with surch arbiatry numbers is still a differnt world > than ouput it in a user-tool like "systemctl show" which could simply > translate it to some meaningful string > no user cares about UINT64_MAX in such outputs quoted from the manual: (systemctl show) "is intended to be

Re: [systemd-devel] systemctl show outputs incorrect MemoryCurrent value

2018-07-25 Thread Reindl Harald
Am 25.07.2018 um 17:49 schrieb Lennart Poettering: > On Mi, 25.07.18 17:06, Reindl Harald (h.rei...@thelounge.net) wrote: > >> Am 25.07.2018 um 17:01 schrieb Lennart Poettering: >>> On Mi, 25.07.18 11:23, George Xie (george...@gmail.com) wrote: >>> thanks for your reply. odds

Re: [systemd-devel] Systemd boot failure in a VM - SOLVED

2018-07-25 Thread Frans de Boer
On 07/20/2018 09:28 PM, Frans de Boer wrote: Dear Reader, I am building my own linux system with systemd, following the directions given by de LFS (linux from scratch) project. Until some time ago all went well, but after systemd 232 (i think) - anyhow right at the time that they start using

Re: [systemd-devel] systemctl show outputs incorrect MemoryCurrent value

2018-07-25 Thread Lennart Poettering
On Mi, 25.07.18 17:06, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 25.07.2018 um 17:01 schrieb Lennart Poettering: > > On Mi, 25.07.18 11:23, George Xie (george...@gmail.com) wrote: > > > >> thanks for your reply. > >> > >> odds enough, on both aforementioned boxes, MemoryAccounting

Re: [systemd-devel] systemctl show outputs incorrect MemoryCurrent value

2018-07-25 Thread Reindl Harald
Am 25.07.2018 um 17:01 schrieb Lennart Poettering: > On Mi, 25.07.18 11:23, George Xie (george...@gmail.com) wrote: > >> thanks for your reply. >> >> odds enough, on both aforementioned boxes, MemoryAccounting is set >> to no: > > On old systemd versions we'd fill in the account props if the

Re: [systemd-devel] systemctl show outputs incorrect MemoryCurrent value

2018-07-25 Thread Lennart Poettering
On Mi, 25.07.18 11:23, George Xie (george...@gmail.com) wrote: > thanks for your reply. > > odds enough, on both aforementioned boxes, MemoryAccounting is set > to no: On old systemd versions we'd fill in the account props if the kernel had the data even if MemoryAccounting was not turned on.

Re: [systemd-devel] systemctl show outputs incorrect MemoryCurrent value

2018-07-25 Thread George Xie
> 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. I have also inspected this possibility, with the following: # systemctl list-units | awk

Re: [systemd-devel] systemctl show outputs incorrect MemoryCurrent value

2018-07-25 Thread Michal Sekletar
On Wed, Jul 25, 2018 at 5:25 AM George Xie 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)

Re: [systemd-devel] Failed to start Apache Tomcat Web Application Container

2018-07-25 Thread Michal Sekletar
On Tue, Jul 24, 2018 at 5:04 PM Mark Huggins wrote: > Question: > Is there way to modify the template file: tomcat.service.erb to include > creating ‘/opt/tomcat/logs/catalina.out' file prior to execution of the 'sudo > systemctl daemon-reload'command? Also, I'm unsure how long the command: >