You are not logged in.
Pages: 1
Hello,
i just installed clean Archlinux in VMware and noticed difference in systemctl status
old installation fully updated:
● systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2017-01-18 14:35:40 CET; 12min ago
Docs: man:systemd-networkd.service(8)
Main PID: 359 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
CGroup: /system.slice/systemd-networkd.service
└─359 /usr/lib/systemd/systemd-networkd
new installation:
● systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2017-01-18 14:04:03 UTC; 48min ago
Docs: man:systemd-networkd.service(8)
Main PID: 489 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 19660)
Memory: 3.5M
CPU: 220ms
CGroup: /system.slice/systemd-networkd.service
└─489 /usr/lib/systemd/systemd-networkd
is there any chance to get the CPU and Memory info on the old system?
Offline
pacman -S dmidecode
dmidecode -t memory
dmidecode -t cpu
cat /proc/cpuinfo
lscpu
i hope this is the answer your looking for
Think Reverse, often it solves the problem
Offline
DefaultCPUAccounting=, DefaultBlockIOAccounting=,
DefaultMemoryAccounting=, DefaultTasksAccounting=
Configure the default resource accounting settings, as configured
per-unit by CPUAccounting=, BlockIOAccounting=, MemoryAccounting=
and TasksAccounting=. See systemd.resource-control(5) for details
on the per-unit settings. DefaultTasksAccounting= defaults to on,
the other three settings to off.
Though this does not explain why CPUAccounting and MemoryAccounting are on by default on the new installation.
Offline
Offline
thanks all
@boosterdev, don't see any connection with systemd status info ??
@loqs, yeah, found that it can be accounting, but it's not applicated on default installation :-(
@slithery, nope, pacdiff shows nothing
i compared systemd confs, compared running "systemd-services" and no difference on both systems
only difference is syslinux on old system vs. efi boot on new instalation
edit://
it's really strange
- new install in vmware on dell notebook - shows info
- same new install in vmware on desktop - no info
- old install up-to-date - no info
i think it's related to mobile CPU, or something different on notebook
Last edited by michi (2017-01-19 23:31:15)
Offline
Pages: 1