On Fri, Jul 11, 2014 at 1:51 PM, Ahmad Samir <ahmadsamir3891(a)gmail.com> wrote:
On 11/07/14 08:27, Balint Szigeti wrote:
>
> On Fri, 2014-07-11 at 13:41 +0800, Ed Greshko wrote:
>
>> On 07/11/14 13:11, Balint Szigeti wrote:
>>>
>>> Can somebody tell me what would happen if I remove Plymouth packages? I
>>> know it handles the boot screen and the user interaction during boot.
>>> Does it mean, if I remove this package I can't examine what happened
>>> during the boot or I can not boot?
>>
>>
>> You'll be able to boot just fine. You'll just see all the
"OK"s
>> scrolling by as the various components are started.
>>
>> Not sure what you're thinking the gain will be to remove it.
>>
>> --
>> If you can't laugh at yourself, others will gladly oblige.
>
>
> $ systemd-analyze blame
> 10.661s systemd-cryptsetup@luks\x2d9ea31b69\x2d8769\x2d4bf1
> \x2d897d\x2d67ecf8d4b0be.service
> 9.862s plymouth-quit-wait.service
> 9.743s accounts-daemon.service
> 8.427s firewalld.service
> improving the boot time :)
>
>
>
As has been said removing the plymouth packages shouldn't prevent the system
from booting (you probably will need to rebuild the initramfs and remove
"rhgb quiet" from the kernel cmd line).
Note that the times in the output don't necessarily mean that
plymouth-quit-wait.service is the reason the boot is slow, from the man
page:
<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>
"systemd-analyze blame" prints a list of all running units, ordered by the
time they took to initialize. This information may be used to optimize
boot-up times. Note that the output might be misleading as the
initialization of one service might slow simply because it waits for the
initialization of another service to complete.
<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
--
Ahmad Samir
systemd-analyze
Startup finished in 1.583s (kernel) + 23.163s (initrd) + 5min 223ms
(userspace) = 5min 24.969s
systemd-analyze blame
4min 44.300s bumblebee-nvidia.service
1min 23.109s plymouth-quit-wait.service
1min 19.944s ModemManager.service
1min 19.639s NetworkManager.service
1min 15.397s chronyd.service
1min 14.720s thinkfan.service
1min 14.146s akmods.service
1min 13.997s akmods-shutdown.service
44.434s rsyslog.service
29.037s accounts-daemon.service
27.259s dnf-makecache.service
18.275s
systemd-cryptsetup(a)luks\x2d62605ed6\x2d6797\x2d48a2\x2d8e3c\x2d0a903b9154fd.service
18.269s
systemd-cryptsetup(a)luks\x2dbbff8fec\x2dd580\x2d48a1\x2d93cb\x2d1daa7cb98aed.service
9.388s systemd-suspend.service
6.910s mcelog.service
6.549s libvirtd.service
6.408s vboxdrv.service
4.642s jexec.service
4.190s proc-sys-fs-binfmt_misc.mount
3.577s polkit.service
3.112s systemd-udev-settle.service
3.047s proc-fs-nfsd.mount
2.972s bluetooth.service
2.911s rtkit-daemon.service
2.851s avahi-daemon.service
2.606s var-lib-nfs-rpc_pipefs.mount
2.180s systemd-logind.service
2.126s lvm2-monitor.service
1.905s fedora-loadmodules.service
1.391s systemd-tmpfiles-clean.service
1.328s systemd-tmpfiles-setup.service
1.324s nfs-lock.service
1.306s fedora-readonly.service
1.188s plymouth-start.service
1.176s tlp.service
1.143s systemd-tmpfiles-setup-dev.service
1.017s fedora-import-state.service
992ms wpa_supplicant.service
937ms systemd-backlight@backlight:acpi_video0.service
907ms dev-hugepages.mount
898ms plymouth-read-write.service
851ms livesys.service
847ms auditd.service
For anyone who thinks they have slow boot.
--
Regards,
Sudhir Khanger.
sudhirkhanger.com
https://github.com/donniezazen