166995 – Misbehavior of the init scripts (net need)

Bug 166995 - Misbehavior of the init scripts (net need)

Summary: Misbehavior of the init scripts (net need)

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] baselayout (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Gentoo's Team for Core System packages

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-02-15 10:07 UTC by Vincent Le Ligeour
Modified:	2007-02-15 10:15 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Vincent Le Ligeour 2007-02-15 10:07:29 UTC

Hi, I have the following problem :
My xen host domains (domU) have 2 interface (eth0 and eth1).
eth0 is setup with kernel parameters and set with noop in /etc/conf.d/net
eth1 is setup only in /etc/conf.d/net
eth0 is not started with init whereas eth1 is.

In runlevel 3 netmount and nfsmount are started before net.eth1 (they requires "net" that is already provided by net.eth0 in the previous runlevel).

The problem is that ALL net interfaces should be started to provide net. I think the problem is related to noop configuration that only "start" noop interfaces and not the others resulting in "net" marked as provide despite all the interfaces are not started.

Target system is x86 with x86 keyword

Comment 1 Vincent Le Ligeour 2007-02-15 10:10:05 UTC

Behavior cannot be reproduce on all domU since I think that services on the same runlevel without dependency are started randomly ?

Comment 2 Jakub Moc (RETIRED) gentoo-dev

2007-02-15 10:15:34 UTC

(In reply to comment #0)
> The problem is that ALL net interfaces should be started to provide net.

If you want this, then you should set RC_STRICT_NET_CHECKING="yes" in /etc/conf.d/rc instead of filing bugs...