Summary: | baselayout 1.12.4-r2: nfs server not started | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | gringotts <gringotts> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
gringotts
2006-08-13 03:26:11 UTC
the point of RC_NET_STRICT_CHECKING=no is that the services get to assume your interfaces are all setup properly that means services can start in any order they feel, so having portmap/nfs start before the net service is legit the "nfs" init.d already depends on the "portmap" service you are right: after verification, the following messages appears: 1. portmap is not started because missing net.eth0 2. nfs is not started because missing portmap In any case, after downgrading baselayout to 1.11.15-r3, I could have a nfs service starting normally. I have verify later than switching from baselayout 1.11 to 1.12 has an effect on portmap and nfs starting or not starting. I left the RC_NET_STRICT_CHECKING variable with her default "no" value. so the behavior you are seeing is correct With baselayout 1.12.4-r2 and -r3, the behaviour was _not_ correct: the services portmap and nfs were not started. Now I have upgrade to baselayout 1.12.4-r6, and the portmap and nfs services are now correctly started. I did not analyze where the difference could come. |