[gentoo-user] What is starting net.eth1 [not in rc-update]

[gentoo-user] What is starting net.eth1 [not in rc-update]

[Harry Putnam]

I don't have an entry for net.eth1 in rc-update show

I don't have any mention of eth1 in /etc/conf.d/net
(only eth0)

Nonetheless something continues to try to start net.eth1 during boot.
What else controls that?  If its not in rc-update or /etc/conf.d/net
it shouldn't happen.

I have a few other boot problems...I'm not sure where they arise from.

hwclock is meddling about during shutdown.
Again, it isn't shown in rc-update 
and /etc/conf.d/hwclock has this in it:

  # If you want to set the Hardware Clock to the current System Time
  # during shutdown, then say "YES" here.  You normally don't need to
  # do this if you run a ntp daemon.
  clock_systohc="NO"

Still, on a shutdown I can't get past this output:
 
 hwclock waiting for localmount
 (Over and over)

I have to hit a manual reset on the computer to get past 
  hwclock waiting for localmount

Also klogd cannot be stopped by reboot or shutdown.  But at least,
unlike hwclock, after a pause the shutdown proceeds anyway.

 eix -Ic openrc
  sys-apps/openrc (0.4.1@12/25/08): OpenRC manages the services, startup
  and shutdown of a host

 eix -Ic udev
  [I] sys-fs/udev (135-r2@12/24/08): Linux dynamic and persistent device
  naming support (aka userspace devfs)

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Ian Lee]

Harry Putnam wrote:
> I don't have an entry for net.eth1 in rc-update show
> 
> I don't have any mention of eth1 in /etc/conf.d/net
> (only eth0)
> 
> Nonetheless something continues to try to start net.eth1 during boot.
> What else controls that?  If its not in rc-update or /etc/conf.d/net
> it shouldn't happen.
> 
> I have a few other boot problems...I'm not sure where they arise from.
> 
> hwclock is meddling about during shutdown.
> Again, it isn't shown in rc-update 
> and /etc/conf.d/hwclock has this in it:
> 
>   # If you want to set the Hardware Clock to the current System Time
>   # during shutdown, then say "YES" here.  You normally don't need to
>   # do this if you run a ntp daemon.
>   clock_systohc="NO"
> 
> Still, on a shutdown I can't get past this output:
>  
>  hwclock waiting for localmount
>  (Over and over)
> 
> I have to hit a manual reset on the computer to get past 
>   hwclock waiting for localmount
> 
> Also klogd cannot be stopped by reboot or shutdown.  But at least,
> unlike hwclock, after a pause the shutdown proceeds anyway.
> 
>  eix -Ic openrc
>   sys-apps/openrc (0.4.1@12/25/08): OpenRC manages the services, startup
>   and shutdown of a host
> 
>  eix -Ic udev
>   [I] sys-fs/udev (135-r2@12/24/08): Linux dynamic and persistent device
>   naming support (aka userspace devfs)
> 
> 

1) net.eth1 problem

There is a udev hook for starting net.* init scripts, 
/lib/udev/rules.d/90-network.rules to be precise


2) Openrc problem
I'm asuming here the openrc problems are from a recent upgrade you have 
done and not inslalled the the runlevels required sadly they are not 
done automatically. Have a look in /usr/share/openrc/runlevels these are 
needed for openrc to work copy any that don't exist in /etc/runlevels 
most important are sysinit and shutdown, boot and default are likey to 
be fine

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 606 bytes --]

Am Sonntag, 28. Dezember 2008 12:50:41 schrieb Ian Lee:

> 2) Openrc problem
> I'm asuming here the openrc problems are from a recent upgrade you have
> done and not inslalled the the runlevels required sadly they are not
> done automatically. Have a look in /usr/share/openrc/runlevels these are
> needed for openrc to work copy any that don't exist in /etc/runlevels
> most important are sysinit and shutdown, boot and default are likey to
> be fine

Hmm, I have the same problem here, but I do have all the directories from 
/usr/share/openrc/runlevels in /etc/runlevels.

Bye...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Ian Lee]

Dirk Heinrichs wrote:
> Am Sonntag, 28. Dezember 2008 12:50:41 schrieb Ian Lee:
> 
>> 2) Openrc problem
>> I'm asuming here the openrc problems are from a recent upgrade you have
>> done and not inslalled the the runlevels required sadly they are not
>> done automatically. Have a look in /usr/share/openrc/runlevels these are
>> needed for openrc to work copy any that don't exist in /etc/runlevels
>> most important are sysinit and shutdown, boot and default are likey to
>> be fine
> 
> Hmm, I have the same problem here, but I do have all the directories from 
> /usr/share/openrc/runlevels in /etc/runlevels.
> 
> Bye...
> 
> 	Dirk
I just found this it might help

http://bugs.gentoo.org/252380

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 168 bytes --]

Am Sonntag, 28. Dezember 2008 15:23:25 schrieb Ian Lee:

> I just found this it might help
>
> http://bugs.gentoo.org/252380

Yes, it did. Thanks a lot.

Bye...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Harry Putnam]

Ian Lee <ian@leehouse.eclipse.co.uk> writes:

> 1) net.eth1 problem
>
> There is a udev hook for starting net.* init scripts,
> /lib/udev/rules.d/90-network.rules to be precise

The script is very brief 
There is no mention of net.eth1 in that script

  SUBSYSTEM=="net", ACTION=="add",    RUN+="net.sh %k start"
  SUBSYSTEM=="net", ACTION=="remove", RUN+="net.sh %k stop"

Further it says not edit this script since it gets overwritten on
update.

Apparently this is not the place to alter what happens at runlevels.


> 2) Openrc problem
> I'm asuming here the openrc problems are from a recent upgrade you
> have done and not inslalled the the runlevels required sadly they are
> not done automatically. Have a look in /usr/share/openrc/runlevels
> these are needed for openrc to work copy any that don't exist in
> /etc/runlevels most important are sysinit and shutdown, boot and
> default are likey to be fine

They are all present in /etc/runlevels.

And again I see no reference to net.eth1 or hwclock

Re: [gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Ian Lee]

Harry Putnam wrote:
> Ian Lee <ian@leehouse.eclipse.co.uk> writes:
> 
>> 1) net.eth1 problem
>>
>> There is a udev hook for starting net.* init scripts,
>> /lib/udev/rules.d/90-network.rules to be precise
> 
> The script is very brief 
> There is no mention of net.eth1 in that script
> 
>   SUBSYSTEM=="net", ACTION=="add",    RUN+="net.sh %k start"
>   SUBSYSTEM=="net", ACTION=="remove", RUN+="net.sh %k stop"
> 
> Further it says not edit this script since it gets overwritten on
> update.
> 
> Apparently this is not the place to alter what happens at runlevels.
> 
> 
>> 2) Openrc problem
>> I'm asuming here the openrc problems are from a recent upgrade you
>> have done and not inslalled the the runlevels required sadly they are
>> not done automatically. Have a look in /usr/share/openrc/runlevels
>> these are needed for openrc to work copy any that don't exist in
>> /etc/runlevels most important are sysinit and shutdown, boot and
>> default are likey to be fine
> 
> They are all present in /etc/runlevels.
> 
> And again I see no reference to net.eth1 or hwclock
> 
> 

that udev rule starts any found network devices on your system net.sh is 
just a  wrapper to the net.* scripts in init.d, if you never use eth1 
then remove net.eth1 from /etc/init.d.

[gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Harry Putnam]

Ian Lee <ian@leehouse.eclipse.co.uk> writes:

>> They are all present in /etc/runlevels.
>>
>> And again I see no reference to net.eth1 or hwclock
>>
>>
>
> that udev rule starts any found network devices on your system net.sh
> is just a  wrapper to the net.* scripts in init.d, if you never use
> eth1 then remove net.eth1 from /etc/init.d.

Well that kind of sucks.  I don't use eth1 often but I do want it in
/etc/init.d.

I'm wondering how wise it is to have tools other than re-update and
/etc/conf.d dinking around with basic services.  It seems like starting
an unwanted ethernet device could even have serious security problems.

Having to remove it from /etc/init.d doesn't sound like a very good
solution either.

Re: [gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

On Mon, 29 Dec 2008 10:39:57 -0600, Harry Putnam wrote:

> Well that kind of sucks.  I don't use eth1 often but I do want it in
> /etc/init.d.
> 
> I'm wondering how wise it is to have tools other than re-update and
> /etc/conf.d dinking around with basic services.  It seems like starting
> an unwanted ethernet device could even have serious security problems.

That's why you would disable hotplugging for network devices in such a
situation, as described much earlier in this thread,


-- 
Neil Bothwick

Assassins do it from behind.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 245 bytes --]

Am Sonntag, 28. Dezember 2008 12:38:37 schrieb Harry Putnam:
> Still, on a shutdown I can't get past this output:
>  
>  hwclock waiting for localmount

I mentioned it in your other thread. Try masking openrc >=0.4.0.

Bye...

	Dirk


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Harry Putnam]

Dirk Heinrichs <dirk.heinrichs@online.de> writes:

> Am Sonntag, 28. Dezember 2008 12:38:37 schrieb Harry Putnam:
>> Still, on a shutdown I can't get past this output:
>>  
>>  hwclock waiting for localmount
>
> I mentioned it in your other thread. Try masking openrc >=0.4.0.

Yeah, just got around to reading that with this nudge.

I've masked it and downgraded but haven't rebooted yet.

I'm looking at Ian Lee's posted URL... maybe those guys are on to something.

[gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Harry Putnam]

Dirk Heinrichs <dirk.heinrichs@online.de> writes:

> Am Sonntag, 28. Dezember 2008 12:38:37 schrieb Harry Putnam:
>> Still, on a shutdown I can't get past this output:
>>  
>>  hwclock waiting for localmount
>
> I mentioned it in your other thread. Try masking openrc >=0.4.0.

I've masked 
   >=sys-apps/openrc-0.4.0

and downlgraded to 
  sys-apps/openrc (0.3.0-r1@12/28/08)

Bootup seems normal except for the fact that something is still trying
to start eth1.

Other things seem to have started normally and no hwclock on shutdown.

So why are there entities beyond /etc/conf.d/net and the controls used
in rc-udpate that can even start things in /etc/init.d?

Aren't those two controls the time honored places to handle that sort
of stuff?

What else is capable of attempting to start services?  Have I been
hacked (.. hehe)

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 369 bytes --]

On Sun, 28 Dec 2008 05:38:37 -0600, Harry Putnam wrote:

> Nonetheless something continues to try to start net.eth1 during boot.
> What else controls that?  If its not in rc-update or /etc/conf.d/net
> it shouldn't happen.

Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf


-- 
Neil Bothwick

I am Flatulus of Borg.  You will be asphixiated.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Dale]

Neil Bothwick wrote:
> On Sun, 28 Dec 2008 05:38:37 -0600, Harry Putnam wrote:
>
>   
>> Nonetheless something continues to try to start net.eth1 during boot.
>> What else controls that?  If its not in rc-update or /etc/conf.d/net
>> it shouldn't happen.
>>     
>
> Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf
>
>
>   

That's in /etc/conf.d/rc on mine.  Has it moved?

Dale

:-)  :-)

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Matt Edens]

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

It is defiantly in hotplug, I have the same thing happen on my gentoo box
with dual gigabit net.  There is a way to stop it from starting but I do not
remember off the top of my head and cant't look quick as I am away from that
box atm on vacation.  Should be something on the wiki that will tell you how
to turn it off.

Matt

On Sun, Dec 28, 2008 at 3:04 PM, Dale <rdalek1967@gmail.com> wrote:

> Neil Bothwick wrote:
> > On Sun, 28 Dec 2008 05:38:37 -0600, Harry Putnam wrote:
> >
> >
> >> Nonetheless something continues to try to start net.eth1 during boot.
> >> What else controls that?  If its not in rc-update or /etc/conf.d/net
> >> it shouldn't happen.
> >>
> >
> > Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf
> >
> >
> >
>
> That's in /etc/conf.d/rc on mine.  Has it moved?
>
> Dale
>
> :-)  :-)
>
>

[-- Attachment #2: Type: text/html, Size: 1250 bytes --]

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

On Sun, 28 Dec 2008 16:06:53 -0800, Matt Edens wrote:

> It is defiantly in hotplug, I have the same thing happen on my gentoo
> box with dual gigabit net.  There is a way to stop it from starting but
> I do not remember off the top of my head and cant't look quick as I am
> away from that box atm on vacation.  Should be something on the wiki
> that will tell you how to turn it off.

That's one of the drawbacks of top posting, it does not
encourage you to look at the mail you are quoting, thus not noticing that
it contains the answer to the question you are posing :(

> 
> > Neil Bothwick wrote:  
> > > On Sun, 28 Dec 2008 05:38:37 -0600, Harry Putnam wrote:
> > >
> > >  
> > >> Nonetheless something continues to try to start net.eth1 during
> > >> boot. What else controls that?  If its not in rc-update
> > >> or /etc/conf.d/net it shouldn't happen.
> > >>  
> > >
> > > Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf
> > >
> > >
> > >  
> >
> > That's in /etc/conf.d/rc on mine.  Has it moved?
> >
> > Dale
> >
> > :-)  :-)
> >
> >  




-- 
Neil Bothwick

In a country of free speech, why are there phone bills?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 328 bytes --]

On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote:

> > Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf


> That's in /etc/conf.d/rc on mine.  Has it moved?

It moved in the switch from baselayout1 to baselayout2/openrc.


-- 
Neil Bothwick

I wonder how much deeper would the ocean be without sponges.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Dale]

Neil Bothwick wrote:
> On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote:
>
>   
>>> Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf
>>>       
>
>
>   
>> That's in /etc/conf.d/rc on mine.  Has it moved?
>>     
>
> It moved in the switch from baselayout1 to baselayout2/openrc.
>
>
>   

Oh, I'm still on baselayout 1 here.  That explains that I guess. 

Dale

:-)  :-) 

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Ian Lee]

Neil Bothwick wrote:
> On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote:
> 
>>> Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf
> 
> 
>> That's in /etc/conf.d/rc on mine.  Has it moved?
> 
> It moved in the switch from baselayout1 to baselayout2/openrc.
> 
> 
This could be what four looking for

http://bugs.gentoo.org/show_bug.cgi?id=206518



Ian

Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

[Ian Lee]

Ian Lee wrote:
> Neil Bothwick wrote:
>> On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote:
>>
>>>> Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf
>>
>>
>>> That's in /etc/conf.d/rc on mine.  Has it moved?
>>
>> It moved in the switch from baselayout1 to baselayout2/openrc.
>>
>>
> This could be what four looking for
> 
> http://bugs.gentoo.org/show_bug.cgi?id=206518
> 
> 
> 
> Ian
> 
try putting rc_coldplug="no" in conf.d/udev or /etc/rc.conf  i would 
assume the udev init script checks both places

[gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Harry Putnam]

Ian Lee <ian@leehouse.eclipse.co.uk> writes:

> Ian Lee wrote:
>> Neil Bothwick wrote:
>>> On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote:
>>>
>>>>> Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf
>>>
>>>
>>>> That's in /etc/conf.d/rc on mine.  Has it moved?
>>>
>>> It moved in the switch from baselayout1 to baselayout2/openrc.
>>>
>>>
>> This could be what four looking for
>>
>> http://bugs.gentoo.org/show_bug.cgi?id=206518
>>
>>
>>
>> Ian
>>
> try putting rc_coldplug="no" in conf.d/udev or /etc/rc.conf  i would
> assume the udev init script checks both places

I can tell you from trying that just now... that is not a good
solution.

First setting rc_coldplug="no" has some very bad effects:
1) caused my KVM switch setup to be ignored completely, where as with
   with the default "yes"  the kvm is recognized soon as I get past
   grub

2) Very strange behavior with the `screen' tool.  I call screen and
   get started but if I do `C-a c' (which should start another screen)
   Instead it prompts me to login and then takes the original screen
   so I can only get one screen, completely defeating the purpose of
   `screen'. 


I'm also wondering about the wisdom introduciing some esoteric places
to control services.  If someone needs sophisticated controls they can
set that up, but for the rest of us  /etc/conf.d and rc-update should
be THE central tools to have basic services started at boot.

There should be nothing scrolling thru the network softlinks
attempting to start anything it finds.

Re: [gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Dale]

Harry Putnam wrote:
> Ian Lee <ian@leehouse.eclipse.co.uk> writes:
>
>   
>> Ian Lee wrote:
>>     
>>> Neil Bothwick wrote:
>>>       
>>>> On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote:
>>>>
>>>>         
>>>>>> Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf
>>>>>>             
>>>>         
>>>>> That's in /etc/conf.d/rc on mine.  Has it moved?
>>>>>           
>>>> It moved in the switch from baselayout1 to baselayout2/openrc.
>>>>
>>>>
>>>>         
>>> This could be what four looking for
>>>
>>> http://bugs.gentoo.org/show_bug.cgi?id=206518
>>>
>>>
>>>
>>> Ian
>>>
>>>       
>> try putting rc_coldplug="no" in conf.d/udev or /etc/rc.conf  i would
>> assume the udev init script checks both places
>>     
>
> I can tell you from trying that just now... that is not a good
> solution.
>
> First setting rc_coldplug="no" has some very bad effects:
> 1) caused my KVM switch setup to be ignored completely, where as with
>    with the default "yes"  the kvm is recognized soon as I get past
>    grub
>
> 2) Very strange behavior with the `screen' tool.  I call screen and
>    get started but if I do `C-a c' (which should start another screen)
>    Instead it prompts me to login and then takes the original screen
>    so I can only get one screen, completely defeating the purpose of
>    `screen'. 
>
>
> I'm also wondering about the wisdom introduciing some esoteric places
> to control services.  If someone needs sophisticated controls they can
> set that up, but for the rest of us  /etc/conf.d and rc-update should
> be THE central tools to have basic services started at boot.
>
> There should be nothing scrolling thru the network softlinks
> attempting to start anything it finds.
>
>
>
>   

If you check mine and Neils post, one of ours will do just what you want
and still allow you to have hotplug set to yes.  It just tells hotplug
not to start networks itself and leave it to your own settings with
rc-update.  There may also be other things that you can set in there as
well. 

Dale

:-)  :-)

Re: [gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Ian Lee]

Dale wrote:
> Harry Putnam wrote:
>> Ian Lee <ian@leehouse.eclipse.co.uk> writes:
>>
>>   
>>> Ian Lee wrote:
>>>     
>>>> Neil Bothwick wrote:
>>>>       
>>>>> On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote:
>>>>>
>>>>>         
>>>>>>> Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf
>>>>>>>             
>>>>>         
>>>>>> That's in /etc/conf.d/rc on mine.  Has it moved?
>>>>>>           
>>>>> It moved in the switch from baselayout1 to baselayout2/openrc.
>>>>>
>>>>>
>>>>>         
>>>> This could be what four looking for
>>>>
>>>> http://bugs.gentoo.org/show_bug.cgi?id=206518
>>>>
>>>>
>>>>
>>>> Ian
>>>>
>>>>       
>>> try putting rc_coldplug="no" in conf.d/udev or /etc/rc.conf  i would
>>> assume the udev init script checks both places
>>>     
>> I can tell you from trying that just now... that is not a good
>> solution.
>>
>> First setting rc_coldplug="no" has some very bad effects:
>> 1) caused my KVM switch setup to be ignored completely, where as with
>>    with the default "yes"  the kvm is recognized soon as I get past
>>    grub
>>
>> 2) Very strange behavior with the `screen' tool.  I call screen and
>>    get started but if I do `C-a c' (which should start another screen)
>>    Instead it prompts me to login and then takes the original screen
>>    so I can only get one screen, completely defeating the purpose of
>>    `screen'. 
>>
>>
>> I'm also wondering about the wisdom introduciing some esoteric places
>> to control services.  If someone needs sophisticated controls they can
>> set that up, but for the rest of us  /etc/conf.d and rc-update should
>> be THE central tools to have basic services started at boot.
>>
>> There should be nothing scrolling thru the network softlinks
>> attempting to start anything it finds.
>>
>>
>>
>>   
> 
> If you check mine and Neils post, one of ours will do just what you want
> and still allow you to have hotplug set to yes.  It just tells hotplug
> not to start networks itself and leave it to your own settings with
> rc-update.  There may also be other things that you can set in there as
> well. 
> 
> Dale
> 
> :-)  :-)
> 

According to the comments hotplugging of services is not allowed by 
default, so why do the net.* services get started?

Re: [gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Dale]

Ian Lee wrote:
> Dale wrote:
>> Harry Putnam wrote:
>>> Ian Lee <ian@leehouse.eclipse.co.uk> writes:
>>>
>>>  
>>>> Ian Lee wrote:
>>>>    
>>>>> Neil Bothwick wrote:
>>>>>      
>>>>>> On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote:
>>>>>>
>>>>>>        
>>>>>>>> Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf
>>>>>>>>             
>>>>>>        
>>>>>>> That's in /etc/conf.d/rc on mine.  Has it moved?
>>>>>>>           
>>>>>> It moved in the switch from baselayout1 to baselayout2/openrc.
>>>>>>
>>>>>>
>>>>>>         
>>>>> This could be what four looking for
>>>>>
>>>>> http://bugs.gentoo.org/show_bug.cgi?id=206518
>>>>>
>>>>>
>>>>>
>>>>> Ian
>>>>>
>>>>>       
>>>> try putting rc_coldplug="no" in conf.d/udev or /etc/rc.conf  i would
>>>> assume the udev init script checks both places
>>>>     
>>> I can tell you from trying that just now... that is not a good
>>> solution.
>>>
>>> First setting rc_coldplug="no" has some very bad effects:
>>> 1) caused my KVM switch setup to be ignored completely, where as with
>>>    with the default "yes"  the kvm is recognized soon as I get past
>>>    grub
>>>
>>> 2) Very strange behavior with the `screen' tool.  I call screen and
>>>    get started but if I do `C-a c' (which should start another screen)
>>>    Instead it prompts me to login and then takes the original screen
>>>    so I can only get one screen, completely defeating the purpose of
>>>    `screen'.
>>>
>>> I'm also wondering about the wisdom introduciing some esoteric places
>>> to control services.  If someone needs sophisticated controls they can
>>> set that up, but for the rest of us  /etc/conf.d and rc-update should
>>> be THE central tools to have basic services started at boot.
>>>
>>> There should be nothing scrolling thru the network softlinks
>>> attempting to start anything it finds.
>>>
>>>
>>>
>>>   
>>
>> If you check mine and Neils post, one of ours will do just what you want
>> and still allow you to have hotplug set to yes.  It just tells hotplug
>> not to start networks itself and leave it to your own settings with
>> rc-update.  There may also be other things that you can set in there as
>> well.
>> Dale
>>
>> :-)  :-)
>>
>
> According to the comments hotplugging of services is not allowed by
> default, so why do the net.* services get started?
>
>
Because it does start them unless that line is in the correct file.  I
ran into this a good while back and had to add that line to mine as
well.  Some of my cards are not even connected to anything and during
boot up it would wait until it timed out before going to the next one. 
I have three cards so that got on my nerves to say the least.  I think
it was set to timeout=forever or timeout=until-dale-is-pissed.  o_O

I would try it and just see if it helps.  If not, nothing lost right?

Dale

:-)  :-) 

Re: [gentoo-user] Re: What is starting net.eth1 [not in rc-update]

[Willie Wong]

On Mon, Dec 29, 2008 at 10:36:08AM -0600, Penguin Lover Harry Putnam squawked:
> > try putting rc_coldplug="no" in conf.d/udev or /etc/rc.conf  i would
> > assume the udev init script checks both places
> 
> I can tell you from trying that just now... that is not a good
> solution.
> 
> First setting rc_coldplug="no" has some very bad effects:
> 1) caused my KVM switch setup to be ignored completely, where as with
>    with the default "yes"  the kvm is recognized soon as I get past
>    grub

I believe this is when rc_coldplug="yes" and rc_plug_services="!*" is
useful. You enable to coldplugging of modules (and thus drive your
kvm) but not start the various services. 

I have rc_plug_services="!net.*" on my laptop. 

> 2) Very strange behavior with the `screen' tool.  I call screen and
>    get started but if I do `C-a c' (which should start another screen)
>    Instead it prompts me to login and then takes the original screen
>    so I can only get one screen, completely defeating the purpose of
>    `screen'. 

That is really strange....

W
-- 
"Nothing is wrong with California that a rise in the ocean level wouldn't cure."
        -- Ross MacDonald
Sortir en Pantoufles: up 752 days, 16:30