Fedora 15 boot delays -

[Bob Goodwin]

On 03/06/11 07:02, Tim wrote:
> On Thu, 2011-06-02 at 14:07 -0400, Bob Goodwin wrote:
>> I was seeing some very slow boot times, probably self inflicted,
>> until I re-installed F-15 after which it worked quite nicely.
>> Until I disabled network manager and set up a non-dhcp network
>> with system-config-network.
>>
>> Then I could connect to the internet by clicking on "Activate"
>> and the browser and e-mail functions worked but there was no
>> connection to the LAN. Ethtool reported there was no device.
> Sound like the old:  Something says NetworkManager is handling your
> ethernet, and things wanting to use the network check to see whether
> NetworkManager has said that the ethernet is up; but because
> NetworkManager didn't bring it up, it says it's down.
>
> The solutions to that were:  Configure NetworkManager to *not* be
> involved in that interface.  Cave in and use NetworkManager to handle
> that interface.
>
>> I then did:
>> cp /etc/sysconfig/network-scripts/ifcfg-p2p1
>> /etc/sysconfig/network-scripts/ifcfg-eth1  and rebooted and eth1
>> came back on and I had access to my NFS, etc.
> This sounds like the:  The new ethernet is *not* called "eth" by
> default, but named as per the BIOS hardware identifies it, yet you (or
> something) expects eth-named devices.
>
>> However the boot routine now stops at "Start LSB: The cups
>> scheduler" and sm-client, 60 seconds at each one which makes for
>> a long boot time. Normally that's only done once a day so it's
>> mostly an annoyance but I would like to fix it so it works right.
> Could be down to the first thing I mentioned:  NetworkManager's still
> considered to be in charge, and things are hanging around waiting for it
> to do its thing.
>
> I seem to recall there was an old thread mentioning that the time-out
> could be adjusted to suit your purposes better.
>
> I think you should have posted with NetworkManager mentioned in the
> subject line, to stand a better chance of catching the attention of
> those more familiar with bludgeoning it into submission.  Boot delays
> could be related to various different things, and the network geeks
> might not read your message.
>

        Interesting points but I've already "thrown in the towel" and
        re-enabled network manager. I'll save your comments in the event
        I am inspired to take another shot at having it my way. This
        works and I can better spend my time doing other things.

        Thanks much.

        Bob
        .