[vz-users] einzelne(n) Messwert(e) direkt in phpmyadmin löschen
Udo1
udo1 at gmx.net
Sun Oct 16 18:47:37 CEST 2016
Am 16.10.2016 um 18:32 schrieb Theo:
> 3.871s networking.service
> 1.091s ntp.service
Das ist ja Müll. Da startet der ntp.service obwohl noch keine
network-service ausgeführt ist?
Aber bei mir das gleiche:
pi at raspberrypi:/etc $ systemd-analyze blame
9.211s dhcpcd.service
5.984s mysql.service
4.327s apache2.service
1.315s systemd-fsck-root.service
978ms systemd-tmpfiles-setup-dev.service
916ms systemd-sysctl.service
717ms systemd-logind.service
707ms networking.service
669ms rc-local.service
641ms keyboard-setup.service
627ms alsa-restore.service
597ms dphys-swapfile.service
592ms triggerhappy.service
532ms avahi-daemon.service
368ms console-setup.service
279ms ntp.service
239ms fake-hwclock.service
214ms systemd-udev-trigger.service
186ms systemd-fsck at dev-mmcblk0p1.service
178ms systemd-setup-dgram-qlen.service
169ms rsyslog.service
166ms kbd.service
144ms systemd-modules-load.service
111ms kmod-static-nodes.service
93ms systemd-journal-flush.service
80ms systemd-random-seed.service
70ms raspi-config.service
68ms systemd-remount-fs.service
68ms boot.mount
56ms sys-kernel-debug.mount
55ms dev-mqueue.mount
46ms systemd-update-utmp.service
43ms systemd-rfkill at rfkill0.service
42ms systemd-tmpfiles-setup.service
38ms plymouth-read-write.service
38ms systemd-user-sessions.service
26ms sys-kernel-config.mount
25ms systemd-udevd.service
24ms plymouth-quit.service
24ms systemd-update-utmp-runlevel.service
19ms udev-finish.service
19ms systemd-tmpfiles-clean.service
14ms plymouth-quit-wait.service
11ms tmp.mount
Sehr komisch.
Gruß
Udo
More information about the volkszaehler-users
mailing list