Hello,
I tried to set memory limits for VE to 12G, but my VE is reporting
something like this:
total used free sharedbuffers cached
Mem: 72718566651672 620184 0 0 0
-/+ buffers/cache:6651672 620184
Swap:
After modify the kmemsize we want to know if we get more fails at
/proc/user_beamcounters.
Can we reset the failcnt to see the new errors?
Thanks in advance.
--
Jorge Fuertes ~ aka Queru
GnuPG key-id: 6B55C7A8
GNU/Linux Reg. User #170191
Presidente Hispalinux (Socio #1510)
http://queru.org
Jorge Fuertes wrote:
Can we reset the failcnt to see the new errors?
Nope, except by stopping and restarting the VE. This is by design, the
reason being that some programs would expect the number to increase and
would be confused if it were to decrease or be 0.
Personally, I think it would
Jorge Fuertes wrote:
After modify the kmemsize we want to know if we get more fails at
/proc/user_beamcounters.
Can we reset the failcnt to see the new errors?
Please see http://wiki.openvz.org/UBC_failcnt_reset
___
Users mailing list
Ok. Thanks, but it can be a good thing, IMHO, for whislist, a failcnt
after last modification.
Bye.
On Jan 28, 2008 12:06 PM, Gregor Mosheh [EMAIL PROTECTED] wrote:
Jorge Fuertes wrote:
Can we reset the failcnt to see the new errors?
Nope, except by stopping and restarting the VE. This is
Hi Peter,
Thanks for the reply. Fortunately, have now got multicast working - see
thread on the Support forum at
http://forum.openvz.org/index.php?t=treegoto=26332#msg_26332 for the
details.
Unfortunately, now the HN network connectivity disappears for a couple of
minutes when I stop the VE.
Hi,
problem was caused by setting:
# Controls which interfaces to send ARP requests and modify APR tables
# on.
NEIGHBOUR_DEVS=detect
this option arived with vzctl version 3.0.22 when I was upgrading from
3.0.18-1dso1.
After I removed that option and restarted HW node all IPv6 hosts get
I've got openvz setup and operating nicely with three VEs (ubuntu7.10, centos4,
redhat9) - but shell job control does not work in any of them.
^Z should suspend the current command inside the VE when in a shell where you've
ssh'd into the VE - but instead it remains inside the current process.
