OpenVZ Forum


Home » General » Support » Documented kernel settings (/etc/sysctl.conf) we can or can not set while inside a CT?
Documented kernel settings (/etc/sysctl.conf) we can or can not set while inside a CT? [message #36932] Fri, 31 July 2009 22:20 Go to previous message
CatDaaaady is currently offline  CatDaaaady
Messages: 7
Registered: September 2008
Location: 94555
Junior Member
Is anyone aware of a documented list of kernel settings that can and can not be changed while inside a container?

This is what I have found so far:
Parameters that can be modified inside the container.
net.ipv4.ip_forward
net.ipv4.conf.default.proxy_arp  
net.ipv4.conf.default.rp_filter  
net.ipv4.conf.default.accept_source_route  
kernel.msgmnb  
kernel.msgmax  
kernel.shmmax  
kernel.shmall  
net.ipv4.conf.all.arp_announce  


Parameters that can NOT be modified inside the container.
kernel.sysrq  
kernel.core_uses_pid  
net.ipv4.tcp_syncookies  
fs.file-max  
net.core.rmem_max  
net.core.wmem_max  
net.core.rmem_default  
net.core.wmem_default 
net.core.optmem_max 
net.core.netdev_max_backlog 

Example: While inside the container doing something like this will not work:
# echo 262070  > /proc/sys/fs/file-max
#  cat /proc/sys/fs/file-max
65535
#


I noticed if am on the hardware node I can change the settings by using "sysctl". But that will affect all the containers on the system.


Is there away to set certain settings for only specific containers and not all of them?
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Main server using x64 bits and VPS using x86
Next Topic: OpenVZ container will not reboot
Goto Forum:
  


Current Time: Tue Sep 03 10:20:56 GMT 2024

Total time taken to generate the page: 0.09572 seconds