Bug 981669 - Boot Time Increased
Summary: Boot Time Increased
Keywords:
Status: CLOSED DUPLICATE of bug 983688
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 19
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-05 12:48 UTC by Himanshu Garg
Modified: 2013-09-13 03:21 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-13 03:21:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Himanshu Garg 2013-07-05 12:48:18 UTC
Description of problem:
After upgrading to Fedora 19 from Fedora 18 using Fedup, additional things have started coming up during boot time which has increased the boot time to over 40 seconds.

Version-Release number of selected component (if applicable): systemd-204-9.fc19.x86_64


How reproducible:


Steps to Reproduce:
1. Boot system
2.
3.

Actual results:

Things come up at boot time.

(1 of 4) A start job is running for firewalld - dynamic firewall daemon

(2 of 4) A start job is running for Wait for Plymouth Boot Screen to Quit

(3 of 4) A start job is running for LSB: Automatically install DKMS modules for new kernels

(4 of 4) A start job is running for Accounts Service

Failed to start Wait for Plymouth Boot Screen to Quit.
See 'systemctl status plymouth-quit-wait.service' for details

Expected results: Boot shoudl be continuous.


Additional info:  After all these, I am able to login but these are causing a lot of wait at boot.

Comment 1 Jóhann B. Guðmundsson 2013-07-05 13:06:11 UTC
Most likely this one "Automatically install DKMS modules for new kernels
"  is causing that delay but in any case please file reports against each service that's causing the delay not systemd. 

You can find out which ones those are by opening a terminal window and run "systemd-analyze blame" and the respectful maintainers that own those components will look at it.

Comment 2 Himanshu Garg 2013-07-10 03:26:29 UTC
I found that on renaming /var/log/journal to /var/log/journal.org, I found no such problem and my boot time is like before.

Comment 3 Lennart Poettering 2013-09-13 03:21:18 UTC
Sounds like 983688

*** This bug has been marked as a duplicate of bug 983688 ***


Note You need to log in before you can comment on or make changes to this bug.