Hi all,
since introduction of systemd my browser autostarts during start-up before the internet connection is established.
So I always have to load my standard tabs manually after.
systemd-analyze blame proides:
711ms dev-sda1.device
709ms user@1000.service
669ms wpa_supplicant.service
398ms lvm2-monitor.service
379ms ModemManager.service
324ms NetworkManager.service
318ms teamviewerd.service
316ms ssh.service
299ms vboxweb.service
259ms lightdm.service
249ms kbd.service
228ms loadcpufreq.service
227ms systemd-udevd.service
212ms systemd-journal-flush.service
148ms virtualbox.service
148ms ntp.service
142ms rsyslog.service
140ms gpm.service
135ms networking.service
127ms systemd-journald.service
117ms console-setup.service
96ms systemd-tmpfiles-setup-dev.service
94ms systemd-modules-load.service
90ms avahi-daemon.service
76ms alsa-restore.service
75ms bluetooth.service
74ms systemd-fsck@dev-disk-by\*.service
74ms kexec.service
73ms acpi-support.service
69ms lm-sensors.service
65ms preload.service
60ms systemd-rfkill.service
58ms polkitd.service
1) Can I influence this?
2) I have no lvm or modem running: Do I need these services to run:
lvm2-monitor.service?
ModemManager.service?
regarding 2:
check the installed packages regarding lvm and modem manager, purge if not needed (that will also kick out the services). same holds for ntp, which has been replaced by systemd-networkd internal service (this info i got in IRC some days ago from agaida)
regarding 1:
i wonder why this is... the network should be up faster than the desktop environment is loaded. how have you yours configured? is this a desktop with wired network only?
there are some other thing one could fix:
* acpid and acpid-support should be deleted, is now systemd
* rsyslog is superseeded by journald - so if one don't use journald with rsyslog, purge it
* kexec-tools are superseeded by systemd and should be purged
Thanks guys, have purged all except lvm (do not find the packs name).
absolut, yes desktop wired only
hi mylo,
regarding lvm:
$ apt-file search lvm2-monitor.service
lvm2: /lib/systemd/system/lvm2-monitor.service
so, its the lvm2 package that needs to be kicked. verify with dpkg -l | grep lvm
can you run the analyze blame again and see whether all is fine?
how is your network connection being created?