| openvz initscript for gentoo [message #8505] | 
			Tue, 21 November 2006 23:10   | 
		 
		
			| 
				
	 | 
 
	
		I had problems using OpenVZ on my Gentoo notebook. Each time I (or  
ifplugd) stop or restart networking, OpenVZ stops. I think it is not  
what we want. 
 
The problem is initscript contains "need net". In fact OpenVZ should  
work fine without networking. 
 
While looking at the bug, I found another one -- OpenVZ modules should  
be loaded after iptables, not before! Perhaps this bug was invisible  
since iptables start before networking, and 'need net' statement was  
preferred to 'before iptables' statement. 
 
The below patch is a solution to both problems. Note that iptables is  
not mentioned since iptables initscript itself has 'before net' so the  
proper order is maintained. 
 
Please review. 
 
diff --git a/etc/init.d/vz-gentoo b/etc/init.d/vz-gentoo 
index ae332c4..46e840f 100644 
--- a/etc/init.d/vz-gentoo 
+++ b/etc/init.d/vz-gentoo 
@@ -4,8 +4,7 @@ # Distributed under the terms of the GNU 
 # $Header:  
 /var/www/viewcvs.gentoo.org/raw_cvs/gentoo-x86/sys-cluster/v zctl/files/vz-3.0.10.initd,v  
1.2 2006/07/09 10:29:24 phreak Exp $ 
  
 depend() { 
-       need net 
-       before iptables 
+       after net 
 } 
  
 check_config() {
		
		
		
 |  
	| 
		
	 | 
 
 
 | 
	
		
		
			| Re: openvz initscript for gentoo [message #8702 is a reply to message #8505] | 
			Sun, 03 December 2006 08:40   | 
		 
		
			
				
				
				
					
						  
						hollow
						 Messages: 2 Registered: December 2006 
						
					 | 
					Junior Member  | 
					 | 
		 
		 
	 | 
 
	
		On Wednesday 22 November 2006 00:10, Kir Kolyshkin wrote: 
> I had problems using OpenVZ on my Gentoo notebook. Each time I (or 
> ifplugd) stop or restart networking, OpenVZ stops. I think it is not 
> what we want. 
> 
> The problem is initscript contains "need net". In fact OpenVZ should 
> work fine without networking. 
> 
> While looking at the bug, I found another one -- OpenVZ modules should 
> be loaded after iptables, not before! Perhaps this bug was invisible 
> since iptables start before networking, and 'need net' statement was 
> preferred to 'before iptables' statement. 
> 
> The below patch is a solution to both problems. Note that iptables is 
> not mentioned since iptables initscript itself has 'before net' so the 
> proper order is maintained. 
> 
> Please review. 
 
looks ok to me, please commit
		
		
		
 |  
	| 
		
	 | 
 
 
 |