| /proc/user_beancounters resetting, [message #26343] | 
			Mon, 21 January 2008 22:20   | 
		 
		
			
				
				
				
					
						  
						Dariush Pietrzak
						 Messages: 40 Registered: November 2007 
						
					 | 
					Member  | 
					 | 
		 
		 
	 | 
 
	
		Does anyone else experience something like that:
 when I stop the VE, and then start it, it's beancounters don't reset,
but, when I stop one VE, and then another one VE, first VE's beancounters 
do get cleaned.
-- 
Key fingerprint = 40D0 9FFB 9939 7320 8294  05E0 BCC7 02C4 75CC 50D9
 Total Existance Failure 
		
		
		
 |  
	| 
		
	 | 
 
 
 | 
	
		
		
			| Re:  /proc/user_beancounters resetting, [message #26351 is a reply to message #26343] | 
			Tue, 22 January 2008 01:33    | 
		 
		
			
				
				
				
					
						  
						Chris Turan
						 Messages: 6 Registered: December 2007 
						
					 | 
					Junior Member  | 
					 | 
		 
		 
	 | 
 
	
		Yes, I have the same issue.  Wait for a minute or two after you've 
stopped the VE.  It takes a few minutes for the kernel to clear it out. 
  Not quite sure why.
For you, it probably has nothing to do with that second VE, only the 
fact that you've waited for a little while.
-Chris
Dariush Pietrzak wrote:
> Does anyone else experience something like that:
>  when I stop the VE, and then start it, it's beancounters don't reset,
> but, when I stop one VE, and then another one VE, first VE's beancounters 
> do get cleaned.
> 
		
		
		
 |  
	| 
		
	 | 
 
 
 | 
	
		
		
			| Re:  /proc/user_beancounters resetting, [message #26355 is a reply to message #26351] | 
			Tue, 22 January 2008 08:04   | 
		 
		
			
				
				
				
					
						  
						dev
						 Messages: 1693 Registered: September 2005  Location: Moscow
						
					 | 
					Senior Member  | 
					 
  | 
		 
		 
	 | 
 
	
		it takes time since TIME WAIT buckets and similar objects should live during some period according to appropriate RFCs.
Chris Turan wrote:
> Yes, I have the same issue.  Wait for a minute or two after you've
> stopped the VE.  It takes a few minutes for the kernel to clear it out.
>  Not quite sure why.
> 
> For you, it probably has nothing to do with that second VE, only the
> fact that you've waited for a little while.
> 
> -Chris
> 
> Dariush Pietrzak wrote:
>> Does anyone else experience something like that:
>>  when I stop the VE, and then start it, it's beancounters don't reset,
>> but, when I stop one VE, and then another one VE, first VE's
>> beancounters do get cleaned.
>>
> 
		
		
		
 |  
	| 
		
	 | 
 
 
 |