You are not logged in.

#1 2014-08-23 19:11:59

callofdutyops
Member
Registered: 2014-08-21
Posts: 9

[SOLVED] networkmanager.service and accounts-daemon.service take slow

Hello everyone!
I have noticed that my laptop booting is slow, then I read the wiki and google around but there seems no answer for me.
It seems that this all because of the NetworkManager, so I post it here.


This is my basic information:

$ uname -a                                                            [3:03:07]
Linux hp 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux

And

$ systemd-analyze                                                     [3:04:25]
Startup finished in 3.363s (firmware) + 1.382s (loader) + 2.824s (kernel) + 24.506s (userspace) = 32.077s

And

$ systemd-analyze blame                                               [3:04:12]
         13.456s NetworkManager.service
         11.414s accounts-daemon.service
          3.289s libvirtd.service
          2.205s gdm.service
          1.094s polkit.service
          1.048s systemd-vconsole-setup.service
           981ms wpa_supplicant.service
           958ms alsa-restore.service
           852ms boot.mount
           636ms systemd-remount-fs.service
           634ms sys-kernel-debug.mount
           609ms dev-hugepages.mount
           569ms sys-kernel-config.mount
           520ms dev-mqueue.mount
           508ms systemd-tmpfiles-setup-dev.service
           506ms tmp.mount
           476ms systemd-udev-trigger.service
           420ms systemd-journal-flush.service
           358ms kmod-static-nodes.service
           268ms systemd-timesyncd.service
           260ms colord.service
           240ms systemd-backlight@backlight:intel_backlight.service
           236ms systemd-update-utmp.service

And

$ systemd-analyze critical-chain                                 [3:07:05]
graphical.target @24.506s
└─multi-user.target @24.506s
  └─libvirtd.service @21.216s +3.289s
    └─network.target @21.142s
      └─NetworkManager.service @7.685s +13.456s
        └─basic.target @7.684s
          └─timers.target @7.683s
            └─systemd-tmpfiles-clean.timer @7.683s
              └─sysinit.target @7.652s
                └─swap.target @7.652s
                  └─dev-disk-by\x2duuid-7006949a\x2d4625\x2d4d7e\x2db101\x2dbe714c525296.swap @7.458s +191ms
                    └─dev-disk-by\x2duuid-7006949a\x2d4625\x2d4d7e\x2db101\x2dbe714c525296.device @7.457s

And

$ journalctl _SYSTEMD_UNIT=accounts-daemon.service 
8月 24 02:49:20 hp accounts-daemon[264]: started daemon version 0.6.37

And

$ journalctl _SYSTEMD_UNIT=NetworkManager.service                     [3:04:39]
8月 24 02:49:12 hp NetworkManager[258]: <info> NetworkManager (version 0.9.10.1) is starting...
8月 24 02:49:12 hp NetworkManager[258]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
8月 24 02:49:12 hp NetworkManager[258]: <info> WEXT support is enabled
8月 24 02:49:12 hp NetworkManager[258]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
8月 24 02:49:20 hp NetworkManager[258]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the Netw
8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_5D05CE
8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_5D05CE 1
8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_1244B0 1
8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_1244B0
8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/9
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/UCWiFi-77777
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/130
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/yangmafu
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/Hotspot
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_281E42
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/NewStar
8月 24 02:49:21 hp NetworkManager[258]: <info> monitoring kernel firmware directory '/usr/lib/firmware'.
8月 24 02:49:21 hp NetworkManager[258]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:07:00
8月 24 02:49:21 hp NetworkManager[258]: <info> WiFi hardware radio set enabled
8月 24 02:49:21 hp NetworkManager[258]: <info> WWAN hardware radio set enabled
8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
8月 24 02:49:21 hp NetworkManager[258]: <info> WiFi enabled by radio killswitch; enabled by state file
8月 24 02:49:21 hp NetworkManager[258]: <info> WWAN enabled by radio killswitch; enabled by state file
8月 24 02:49:21 hp NetworkManager[258]: <info> WiMAX enabled by radio killswitch; enabled by state file
8月 24 02:49:21 hp NetworkManager[258]: <info> Networking is enabled by state file
8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): link connected
8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): carrier is ON
8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): carrier is OFF
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): new Ethernet device (driver: 'r8169' ifindex: 2)
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): exported as /org/freedesktop/NetworkManager/Devices/1
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): preparing device
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): created default wired connection 'Wired connection 1'
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): using nl80211 for WiFi device control
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): driver supports Access Point (AP) mode
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): new 802.11 WiFi device (driver: 'rt2800pci' ifindex: 3)
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): exported as /org/freedesktop/NetworkManager/Devices/2
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): preparing device
8月 24 02:49:23 hp NetworkManager[258]: <info> wpa_supplicant started
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: starting -> ready
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): device state change: unavailable -> disconnected (reason 'supplicant-available')
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: ready -> disconnected
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: disconnected -> inactive
8月 24 02:49:25 hp NetworkManager[258]: <info> Auto-activating connection 'NewStar'.
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) scheduled...
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) started...
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
8月 24 02:49:25 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTING
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) scheduled...
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) complete.
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) starting...
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: prepare -> config (reason 'none') [40 50 0]
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1/wireless): connection 'NewStar' has security, and secrets exist.  No ne
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): exported as /org/freedesktop/NetworkManager/Devices/1
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): preparing device
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): created default wired connection 'Wired connection 1'
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): using nl80211 for WiFi device control
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): driver supports Access Point (AP) mode
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): new 802.11 WiFi device (driver: 'rt2800pci' ifindex: 3)
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): exported as /org/freedesktop/NetworkManager/Devices/2
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): preparing device
8月 24 02:49:23 hp NetworkManager[258]: <info> wpa_supplicant started
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: starting -> ready
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): device state change: unavailable -> disconnected (reason 'supplicant-available')
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: ready -> disconnected
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: disconnected -> inactive
8月 24 02:49:25 hp NetworkManager[258]: <info> Auto-activating connection 'NewStar'.
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) starting connection 'NewStar'
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) scheduled...
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) started...
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
8月 24 02:49:25 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTING
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) scheduled...
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) complete.
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) starting...
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: prepare -> config (reason 'none') [40 50 0]
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1/wireless): connection 'NewStar' has security, and secrets exist.  No ne
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'ssid' value 'NewStar'
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'scan_ssid' value '1'
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'auth_alg' value 'OPEN'
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'psk' value '<omitted>'
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) complete.
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: set interface ap_scan to 1
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: inactive -> authenticating
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: authenticating -> associating
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: associating -> associated
8月 24 02:49:26 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: associated -> 4-way handshake
8月 24 02:49:26 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: 4-way handshake -> completed
8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wir
8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1) Stage 3 of 5 (IP Configure Start) scheduled.
8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1) Stage 3 of 5 (IP Configure Start) started...
8月 24 02:49:26 hp NetworkManager[258]: <info> (wlo1): device state change: config -> ip-config (reason 'none') [50 70 0]
8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1) Beginning DHCPv4 transaction (timeout in 45 seconds)
8月 24 02:49:27 hp NetworkManager[258]: <info> dhcpcd started with pid 346
8月 24 02:49:27 hp NetworkManager[258]: <info> Activation (wlo1) Stage 3 of 5 (IP Configure Start) complete.
8月 24 02:49:27 hp dhcpcd[346]: version 6.4.3 starting
8月 24 02:49:27 hp NetworkManager[258]: <info> (wlo1): DHCPv4 state changed nbi -> preinit
8月 24 02:49:27 hp dhcpcd[346]: DUID 00:01:00:01:1b:84:72:e9:b8:76:3f:39:7c:5b
8月 24 02:49:27 hp dhcpcd[346]: wlo1: IAID 3f:39:7c:5b
8月 24 02:49:27 hp dhcpcd[346]: wlo1: soliciting an IPv6 router
8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: version 6.4.3 starting
8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: DUID 00:01:00:01:1b:84:72:e9:b8:76:3f:39:7c:5b
8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: wlo1: IAID 3f:39:7c:5b
8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: wlo1: soliciting an IPv6 router
8月 24 02:49:28 hp dhcpcd[346]: wlo1: rebinding lease of 192.168.1.100
8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: wlo1: rebinding lease of 192.168.1.100
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): carrier is OFF
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): new Bridge device (driver: 'bridge' ifindex: 4)
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): exported as /org/freedesktop/NetworkManager/Devices/3
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): preparing device
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
8月 24 02:49:32 hp dhcpcd[346]: wlo1: leased 192.168.1.100 for 7200 seconds
8月 24 02:49:32 hp dhcpcd[346]: wlo1: adding route to 192.168.1.0/24
8月 24 02:49:32 hp NetworkManager[258]: dhcpcd[346]: wlo1: leased 192.168.1.100 for 7200 seconds
8月 24 02:49:32 hp NetworkManager[258]: dhcpcd[346]: wlo1: adding route to 192.168.1.0/24
8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): DHCPv4 state changed preinit -> reboot
8月 24 02:49:33 hp NetworkManager[258]: <info>   address 192.168.1.100
8月 24 02:49:33 hp NetworkManager[258]: <info>   plen 24 (255.255.255.0)
8月 24 02:49:33 hp NetworkManager[258]: <info>   gateway 192.168.1.1
8月 24 02:49:33 hp NetworkManager[258]: <info>   server identifier 192.168.1.1
8月 24 02:49:33 hp NetworkManager[258]: <info>   lease time 7200
8月 24 02:49:33 hp NetworkManager[258]: <info>   nameserver '192.168.1.1'
8月 24 02:49:33 hp NetworkManager[258]: nm_ip4_config_add_nameserver: assertion 'new != 0' failed
8月 24 02:49:33 hp NetworkManager[258]: <info>   nameserver '0.0.0.0'
8月 24 02:49:33 hp NetworkManager[258]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
8月 24 02:49:33 hp NetworkManager[258]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Commit) started...
8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
8月 24 02:49:33 hp NetworkManager[258]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Commit) complete.
8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): device state change: secondaries -> activated (reason 'none') [90 100 0]
8月 24 02:49:33 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTED_LOCAL
8月 24 02:49:34 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTED_GLOBAL
8月 24 02:49:34 hp NetworkManager[258]: <info> Policy set 'NewStar' (wlo1) as default for IPv4 routing and DNS.
8月 24 02:49:34 hp NetworkManager[258]: <info> Writing DNS information to /usr/bin/resolvconf
8月 24 02:49:35 hp NetworkManager[258]: <info> Activation (wlo1) successful, device activated.
8月 24 02:49:35 hp NetworkManager[258]: <info> startup complete
8月 24 02:49:40 hp dhcpcd[346]: wlo1: no IPv6 Routers available
8月 24 02:49:40 hp NetworkManager[258]: dhcpcd[346]: wlo1: no IPv6 Routers available

Last edited by callofdutyops (2014-08-26 14:48:22)

Offline

#2 2014-08-26 07:20:15

MA131D
Member
Registered: 2013-06-08
Posts: 2

Re: [SOLVED] networkmanager.service and accounts-daemon.service take slow

hello

mine have the same problem  boot take 2 min
what i did  to solve problem is   delete the files that inside journal file you can find it in  /var/log/journal/    but  first take backup of that file then delete

Offline

#3 2014-08-26 10:56:50

callofdutyops
Member
Registered: 2014-08-21
Posts: 9

Re: [SOLVED] networkmanager.service and accounts-daemon.service take slow

MA131D wrote:

hello

mine have the same problem  boot take 2 min
what i did  to solve problem is   delete the files that inside journal file you can find it in  /var/log/journal/    but  first take backup of that file then delete

Thanks a lot! I'll try.

Update:
This really did a great job!

4.683s NetworkManager.service
2.680s libvirtd.service
2.305s accounts-daemon.service
1.238s alsa-restore.service

But I wonder whether there's some improvement?

Update:
Ok, seems there's no better answer, but I think this enough for me. Mark it SOLVED
I delete the journal files and

sudo vim /etc/systemd/journald.conf
uncomment SystemMaxUse= 
let it equals 50M (depends on you)

Last edited by callofdutyops (2014-08-26 14:47:57)

Offline

#4 2014-08-26 16:40:34

ooo
Member
Registered: 2013-04-10
Posts: 1,637

Re: [SOLVED] networkmanager.service and accounts-daemon.service take slow

callofdutyops wrote:

But I wonder whether there's some improvement?

Do you mean why there's an improvement after removing the journal files?

first of all, I hope that you know what systemd journal is, and what files you just deleted.

systemd journal stores all system logs in database files in /var/log/journal/
every time you boot up your system, journald will log the entire boot process and stores in its database (and continue logging of course).
over time the journal will get huge (unless you limit its size) and fragmented, which could slow down reading and writing from the it greatly.
so, if writing the log during the boot process slows down greatly, it will certainly have an detrimental effect on overall boot speed.

I hope that makes sense :)

I think I saw this mentioned on some systemd TODO list, so developers should aware of this and possibly trying to figure out some workaround.
In the meantime limiting journal size is probably a good idea.

If you happened to be using btrfs, disabling COW for files in /var/log/journal and 'autodefrag' mount option may also help some.
also defragmenting the files in /var/log/journal if your file system supports it

Last edited by ooo (2014-08-26 16:42:10)

Offline

#5 2014-08-28 13:49:08

callofdutyops
Member
Registered: 2014-08-21
Posts: 9

Re: [SOLVED] networkmanager.service and accounts-daemon.service take slow

ooo wrote:
callofdutyops wrote:

But I wonder whether there's some improvement?

Do you mean why there's an improvement after removing the journal files?

first of all, I hope that you know what systemd journal is, and what files you just deleted.

systemd journal stores all system logs in database files in /var/log/journal/
every time you boot up your system, journald will log the entire boot process and stores in its database (and continue logging of course).
over time the journal will get huge (unless you limit its size) and fragmented, which could slow down reading and writing from the it greatly.
so, if writing the log during the boot process slows down greatly, it will certainly have an detrimental effect on overall boot speed.

I hope that makes sense smile

I think I saw this mentioned on some systemd TODO list, so developers should aware of this and possibly trying to figure out some workaround.
In the meantime limiting journal size is probably a good idea.

If you happened to be using btrfs, disabling COW for files in /var/log/journal and 'autodefrag' mount option may also help some.
also defragmenting the files in /var/log/journal if your file system supports it

First of all, thanks to your very clear explanation!
English is not my mother tongue, so I think I express me in a wrong way.Sorry for this!

What I exactly want to mean is that is it possible to make booting more faster?

Offline

#6 2014-08-28 19:16:37

ooo
Member
Registered: 2013-04-10
Posts: 1,637

Re: [SOLVED] networkmanager.service and accounts-daemon.service take slow

No worries, I'm not native speaker either, so I can certainly understand :)

callofdutyops wrote:

What I exactly want to mean is that is it possible to make booting more faster?

Unfortunately there's no simple answer, but probably yes.
Basically it comes down to figuring out what's slowing down your system bootup, and working around or fixing those issues if possible.

If NetworkManager is slowing you down, possible workaround could be changing its .service file to make it start on background.
I described how to do that here. Note that there could be issues if some of your startup services require network connection.

Also, check out Improve boot performance wiki article for some tips if you haven't already.

Installing linux-ck from graysky's repo or AUR might be beneficial for boot speed as well as your system's overall performance, by enabling BFQ io-scheduler and Brain Fuck Scheduler.
Both are experimental, but should work quite stably, especially now as certain long standing bug was just fixed in BFS.

Offline

#7 2014-08-30 02:03:26

callofdutyops
Member
Registered: 2014-08-21
Posts: 9

Re: [SOLVED] networkmanager.service and accounts-daemon.service take slow

ooo wrote:

Unfortunately there's no simple answer, but probably yes.

I have searched your tips, yes, they are all complex method almost.
I'm afraid to make my arch dead , so I think I'll stop here. smile

Thanks a lot, again.

Offline

#8 2015-01-20 20:50:55

roberthchan
Member
Registered: 2015-01-20
Posts: 1

Re: [SOLVED] networkmanager.service and accounts-daemon.service take slow

Thank you works in opensuse 13.2 i think that is happen when migrate to Rolling relase, peace!

Offline

Board footer

Powered by FluxBB