I think it is currently "none" by default in baselayout-vserver. I think it should be "no" at least (probably as in normal baselayout) because otherwise some services (like lighttpd) randomly fail to start with something like: 2006-10-01 03:10:55: (network.c.300) can't bind to port: 10.0.0.201 80 Cannot assign requested address although they "need net", because there is a race condition and sometimes venet isn't up yet. Setting it to "no" seems to solve the problem reliably. Thanks to pioto@irc for helping me track this down and suggesting bug report.
i don't think we should/will change this setting in baselayout-vserver, because of 1) linux-vserver does not use a virtualized network approach, but a isolated one, where the IP adresses are assigned before the virtual server has started 2) baselayout-vserver will fade away in the near future (with baselayout-1.13) 3) the RC_NET_STRICT_CHECKING setting will probably go away (see http://article.gmane.org/gmane.linux.gentoo.devel/43441)
(In reply to comment #1) > i don't think we should/will change this setting in baselayout-vserver, Well, I will not try to push that change but with openvz you are getting subtle and hard to debug timing errors while starting packages with this default. I spent a few hours debuging what and why is this and it wasn't very nice thing to do. ;-) And somebody that does not know network programming, bash and Gentoo init scripts may have worse problems. So maybe at least add a warning into Gentoo VPS howto?
