You are not logged in.

#1 2021-07-19 16:14:22

ZenRen
Member
Registered: 2020-05-08
Posts: 24

nmb.service greatly slowing down boot time

My systemd-analyze critical-chain shows the following:

graphical.target @11.848s
└─multi-user.target @11.848s
  └─smb.service @11.767s +80ms
    └─nmb.service @778ms +10.986s
      └─network-online.target @775ms
        └─network.target @775ms
          └─wpa_supplicant.service @1.633s +9ms
            └─dbus.service @734ms
              └─basic.target @732ms
                └─sockets.target @732ms
                  └─dbus.socket @732ms
                    └─sysinit.target @730ms
                      └─systemd-backlight@backlight:amdgpu_bl0.service @2.027s +4ms
                        └─system-systemd\x2dbacklight.slice @652ms
                          └─system.slice @237ms
                            └─-.slice @237ms

I do use nmb, but it is not necessary to wait for it to reach graphical.target. I use my laptop at work and just use it to access Windows shares... its currently half baked, but it works, I have not actually tried hostname resolution and I don't actually know if it works correctly, I know I can't ping my domain controller by hostname, so that is not a good sign. None of that is really a big deal, I just don't want it to wait for nmb and smb to reach userspace.

What should I do here? Can I just add graphical.target to the line:

After=network.target network-online.target

What about multi-user.target? Its not like I need them to log into my computer, but I don't want them to function incorrectly, like I can't access share folders within kde.

Last edited by ZenRen (2021-07-19 16:18:46)

Offline

Board footer

Powered by FluxBB