Re: 108 seconds to start F18 64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2013-01-07 15:28 (GMT-0800) Adam Williamson composed:

On Mon, 2013-01-07 at 18:22 -0500, Felix Miata wrote:

On 2013-01-07 18:05 (GMT-0500) Felix Miata composed:

> On 2013-01-07 12:46 (GMT+0100) Matthias Runge composed:

>> On 01/07/2013 12:28 PM, Felix Miata wrote:

>>> Also, several seconds for login prompt to appear on each tty where
>>> not previously used on that boot.

>>> cmdline: root=LABEL=h50root13 rd.md=0 rd.lvm=0 rd.dm=0 FONT=True
>>> KEYMAP=us rd.luks=0 LANG=en_US.UTF-8 splash=verbose video=1152x864@70 3

>>> /var/log/boot.log:
>>> http://fm.no-ip.com/Tmp/Linux/bootlog-f18-big41.txt

>>> What needs to be installed to capture messages from before
>>> reaching target Basic System? tty1 is cleared, and I can never
>>> remember how to prevent that, or find instructions to do so, since
>>> systemd replaced sysvinit. :-(

>> Instead you should:

>> yum install systemd-analyze

>> and then execute systemd-analyze blame
>> or systemd-analyze plot > bootchart.svg
>> (probably the latter, and please post that graphic somewhere)

> Thanks!

> http://fm.no-ip.com/Tmp/Linux/bootchart-big41-f18.svg

> FWIW, on the 98s boot in this graphic, the occasional use eSATA device
> counted within the 108s was powered down.

Another with the eSATA device powered at POST, and with clock corrected for
non-working NTP (0.5s shorter):
http://fm.no-ip.com/Tmp/Linux/bootchart-big41-f18b.svg

Waiting on every login prompt on a tty is very annoying. Can they be
configured to start at boot instead of on demand? When booting with 3 on
cmdline it seems nuts that they don't.

Yes, you'd just have to adjust the systemd service config for
getty@.service .

I've yet to stumble onto a reliable doc for dealing with that file, which is a symlink to /usr/lib/systemd/system/getty@.service. There is no man page for getty@.service or getty@tty1.service. I've seen bits here and there on getting tty1 to not clear, but I never manage to get it to not happen without multiple reconfiguration attempts, and reboots.

 But the spawning should be just about instantaneous on
any reasonable config. If you have to wait for the tty to appear that
sounds like a bug.

It happens on Cauldron too, but the delay is much longer on F18.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test



[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux