Tony, My point is that OpenVZ containers will not show *any* swap space available or in use, because there isn't any. There can't be because containers don't work like that. If this were a KVM or VMware virtual machine (something powered by a hypervisor of sorts), obviously there's be a swap partition. But it's not really a virtual machine. :)
So, OpenVZ presents "some memory" to the container. The "some memory" comes from the host system and can be divided between swap and physical it seems. -- Robert Tony Graziano wrote: > When you start having swap space you need to understand the difference > between "available" and "in use". > > I've always understood that when swap becomes "in use", you would begin to > experience performance degradation related to the percentage "in use". > > Hope that your changes work out for you, looks interesting. Nice that it > shows no swap in use. > ============================ > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: tgrazi...@myitdepartment.net > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
