Choose style:

Author Topic: P7: Removing Samba made shutdown very slow ( from 2 secs to 58 secs)  (Read 2604 times)

0 Members and 1 Guest are viewing this topic.

Offline berliner58

  • Jr. Member
  • **
  • Posts: 66
  • Karma: 4
  • New Forum User
    • View Profile
  • Peppermint version(s): Peppermint 8
Re: P7: Removing Samba made shutdown very slow ( from 2 secs to 58 secs)
« Reply #15 on: October 12, 2016, 03:15:15 am »
I tested it, but the boot still takes 32 seconds.
Edit: I removed apparmor, now booting takes about 29 seconds.

systemd-analyze critical-chain
Code: [Select]
franz@franz-Inspiron-560 ~ $ 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 @24.420s
└─multi-user.target @24.420s
  └─smbd.service @24.114s +305ms
    └─nmbd.service @22.426s +1.671s
      └─network-online.target @22.412s
        └─NetworkManager-wait-online.service @13.957s +8.455s
          └─NetworkManager.service @10.973s +2.963s
            └─dbus.service @10.488s
              └─basic.target @10.401s
                └─paths.target @10.401s
                  └─systemd-networkd-resolvconf-update.path @10.401s
                    └─sysinit.target @10.341s
                      └─systemd-update-utmp.service @10.207s +133ms
                        └─systemd-tmpfiles-setup.service @10.069s +117ms
                          └─local-fs.target @10.032s
                            └─home.mount @9.986s +46ms
                              └─systemd-fsck@dev-disk-by\x2duuid-fcd68866\x2d701
                                └─local-fs-pre.target @9.572s
                                  └─lvm2-monitor.service @1.693s +7.879s
                                    └─lvm2-lvmetad.service @2.474s
lines 1-23

I don't understand why it takes 9 seconds for the lvm2-monitor.service.
When I install a linux-OS, I never ever select the option to use  lvm , so the lvm2-monitor.service waits in vain, or am I wrong ?

I have the impression that I cannot reduce the NetworkManager-wait-online.service, so those 9 seconds must be accepted ?

Here is systemd-anazlyze blame
Spoiler (click here to view / hide)
franz@franz-Inspiron-560 ~ $ systemd-analyze blame
         11.872s apt-daily.service
          8.455s NetworkManager-wait-online.service
          7.879s lvm2-monitor.service
          7.248s dev-sda5.device
          4.453s mintsystem.service
          2.963s NetworkManager.service
          2.438s ufw.service
          2.367s ModemManager.service
          1.933s plymouth-start.service
          1.819s udisks2.service
          1.729s accounts-daemon.service
          1.682s systemd-tmpfiles-setup-dev.service
          1.671s nmbd.service
          1.554s samba-ad-dc.service
          1.328s networking.service
           989ms lightdm.service
           985ms irqbalance.service
           962ms grub-common.service
           938ms console-setup.service
           845ms systemd-udevd.service
           822ms keyboard-setup.service
           790ms systemd-modules-load.service
           761ms ondemand.service
lines 1-23
[close]
« Last Edit: October 13, 2016, 04:05:49 am by berliner58 »
P8 x64 Desktop Dual core Pentium E5400 (-MCP-) RAM: 8GB