On 05/10/2019 15:09, Terry Coles wrote:
Hi,

My Dell XPS 13 has always been very slow to boot and I just put up with it
because I use my desktop PC for most serious work.

However, I stumbled across an article in a magazine which informed me about
systemd-analyze, so I tried it.  Here is the output:

terry@XPS-13:~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@"
character.
The time the unit takes to start is printed after the "+" character.

graphical.target @56.633s
└─multi-user.target @56.633s
   └─smbd.service @56.563s +69ms
     └─nmbd.service @6.501s +50.060s
       └─network-online.target @6.470s
         └─NetworkManager-wait-online.service @1.822s +4.647s
           └─NetworkManager.service @1.684s +136ms
             └─dbus.service @1.679s
               └─basic.target @1.581s
                 └─sockets.target @1.581s
                   └─snapd.socket @1.574s +6ms
                     └─sysinit.target @1.569s
                       └─systemd-timesyncd.service @1.157s +411ms
                         └─systemd-tmpfiles-setup.service @1.123s +30ms
                           └─systemd-journal-flush.service @930ms +189ms
                             └─systemd-journald.service @139ms +724ms
                               └─systemd-journald.socket @137ms
                                 └─system.slice @134ms
                                   └─-.slice @134ms

As you can see, the culprit seems to be nmbd.service; over 50 seconds
compared to the next worse item of 4.6 seconds.  This laptop is running
Kubuntu 19.04 as is the desktop. I am aware that nmbd (and smbd) are related
to samba and I previously setup a samba server on the laptop to assist with
sharing files but I don't currently on the desktop (I used to share my
directories on the desktop, but I did a clean installation on the desktop
because of a bug in qt).

It is still useful to have samba, but am unsure why the nmbd service takes so
long.  Any ideas?

Ran it on my Desktop, running Kubuntu 18.04, with this result:

peterm@peterm-MBB-34204H:~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @30.820s
└─multi-user.target @30.820s
  └─mpd.service @23.584s +7.235s                          *
    └─network.target @23.579s
      └─NetworkManager.service @21.242s +2.336s  *
        └─dbus.service @21.233s
          └─basic.target @21.192s
            └─sockets.target @21.192s
              └─snapd.socket @21.125s +66ms  *
                └─sysinit.target @21.032s
                  └─systemd-timesyncd.service @20.802s +229ms  *
                    └─systemd-tmpfiles-setup.service @20.565s +97ms *
                      └─systemd-journal-flush.service @3.401s +17.163s *
                        └─systemd-remount-fs.service @3.229s +171ms   *
                          └─systemd-journald.socket @3.202s
                            └─system.slice @3.202s
                              └─-.slice @3.183s


'*' marks those highlighted in pink(?).

Peter


--
 Next meeting: BEC, Bournemouth, Tuesday, 2019-10-01 20:00
 Check to whom you are replying
 Meetings, mailing list, IRC, ...  http://dorset.lug.org.uk/
 New thread, don't hijack:  mailto:dorset@mailman.lug.org.uk

Reply via email to