F15 long boot time/cups scheduler problem

[Ian Malone]

On 27 May 2011 12:34, Bob Goodwin <bobgoodwin at wildblue.net> wrote:
> On 27/05/11 06:51, Bob Goodwin wrote:
>> On 27/05/11 06:02, Ian Malone wrote:
>>> Was hesitating to suggest you might have the same problem I did, as it
>>> looks to be stopping at a different point, but it's maybe worth
>>> checking you don't have lots of connections specified in
>>> /etc/sysconfig/network-scripts/ifcfg-*
>>> https://bugzilla.redhat.com/show_bug.cgi?id=708207
>>>
>>
>>        I don't even show ifcfg-eth1 in:
>>
>>        /etc/sysconfig/network-scripts/ifcfg-*
>>
>>        Only a line for 127.0.0.1 with a few items, looks normal.
>>
>>        So that may be what's causing problems. I will try creating it.
>>        The boot process also stops momentarily at NFS too, but that's
>>        perhaps a second or two so I thought that might be normal? The
>>        60 seconds at cups scheduler got my attention.
>>
>>        I will let you know the result.
>>
>>        Bob
>>
>>
>
>    Ok, I created the script file referring to the one in the working
>    F-14 box9. The symptoms are different but I may not have the script
>    entries exactly right?
>
>        [bobg at box6 ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1
>
>
>        DEVICE=eth1
>        IPADDR=192.168.1.6
>        NETMASK=255.255.255.0
>        BOORPROTO=none
>        ONBOOT=yes
>        TYPE=Ethernet
>        NM_CONTROLLED=no
>        USERCTL=yes
>        IPV6INIT=yes
>        DNS2=208.67.220.220
>        DNS1=208.67.222.222
>        PREFIX=24
>        GATEWAY=192.168.1.1
>
>    I'm not sure about the PREFIX item?
>
>    Now it pauses about 15 sec at Cups Scheduler and then stumbles over
>    "sm-client" a bit longer.
>
>    I suspect this may be related to the problem, now to get this
>    configuration file right. any suggestions appreciated.
>
>    Bob
>
>    Note: I've rsync'd the two thunderbird mails and am working from the
>    F-15 computer now. Stuff seems to work fine, just the boot
>    "problem," not a major thing, just annoying.
>
>

My particular problem was the system was attempting to connect to
everything that had an ifcfg-X, and waited for that to finish. Sounds
like yours isn't quite the same, but related to the particular network
setup.

-- 
imalone