jesin
deepin
2018-01-01 19:08 把默认timeout=30s改小一点就行了
Reply Like 0 View the author
https://bbs.deepin.org/post/150831
没有ssd,省钱玩个鸡?
没有电脑的区别,只有hdd,和ssd的区别。
https://bbs.deepin.org/post/150831
建议把docker.service和php设为手动启动吧。

https://bbs.deepin.org/post/150831
在ubuntu下:
https://bbs.deepin.org/post/150831
我也来晒晒
lxflhy@lxflhy-PC:~$ systemd-analyze
Startup finished in 11.236s (kernel) + 31.857s (users ...

https://bbs.deepin.org/post/150831
為什么你 NetworkManager 需要花这么久的时间?
dzuiuabi 发表于 2018-1-7 13:56
比我快
https://bbs.deepin.org/post/150831
本来蛮快的,整那个4.14测试版,给整慢了,每次开机都会有个啥东西加载失败顿了一会 ...


https://bbs.deepin.org/post/150831
$ systemd-analyze
Startup finished in 3.801s (kernel) + 7.432s (userspace) = 11.234s
渣渣笔记本的[sm ...
Popular Events
More
然后在看看是什么东西这么拖后退。
于是我找了一些资料
[page]
[size=13.3333px]Hi
[size=13.3333px]I see
[size=13.3333px]Code:
7.872s NetworkManager-wait-online.service
[size=13.3333px]when I run a
[size=13.3333px]Code:
systemd-analyze blame
[size=13.3333px]Is this normal?
[size=13.3333px]Seems like it is adding a LOT of time to my boot.
[size=13.3333px]Any way to optimize?
[size=13.3333px]Centos 7 + MATE install
[size=13.3333px]
[size=13.3333px]有人就回复了:
Nope.
the problem is that systemd assumes the network is ready for use as soon as it starts NetworkManager.
When this is the case, nearly all network dependent actions fail - from network based filesystems, name lookups, time synchronization, databases, network user identifications (LDAP/NIS/...).
So much fails that the systemd developers had to start modifying a ton of other applications (this one being NetworkManager).
NetworkManager-wait-online is required to delay until the network is usable. This required modification of NetworkManager to explicitly send a "ready" signal back to systemd. This normally works (DHCP clients got modified too). And even the database servers got modified for the same reason.
This is one of the reasons systemd is considered a poor design, and imposes a LOT of things on services.
意思就是这个服务必须要这样启动?网络服务,总而言之,很糟糕,我可能是这个论坛开机醉酒的用户