On Sat 2011-12-17 (14:38), DTK wrote:
I am trying to avoid having to install NTP in every container, so I
came up with following idea.
Main server cron job
* 0 * * * /sbin/hwclock -w
Each container has following cron job
10 0 * * * /sbin/hwclock -s
However, the
2011/12/18 DTK grues...@gmail.com:
I am trying to avoid having to install NTP in every container, so I
came up with following idea.
Main server cron job
* 0 * * * /sbin/hwclock -w
Each container has following cron job
10 0 * * * /sbin/hwclock -s
However, the container
What could be worse than a cgroup is not deleted by lxc-destroy? Why,
inability to create a cgroup using lxc-create!
Seriously, the host machine can not start vservers anymore. This is after
one of the cgroups got stuck in the unremovable state.
With these issues it becomes harder and harder for
On Dec 18, 2011 1:09 PM, Jérôme Petazzoni jerome.petazz...@dotcloud.com
wrote:
If that happens, just try to terminate the other processes running in the
cgroup, rename it (mv /cgroup/mylittlecontainer /cgroup/broken) and
restart it.
This saved me a few reboots already :-)
You should be able to
On 12/18/2011 11:56 AM, C Anthony Risinger wrote:
On Dec 18, 2011 1:09 PM, Jérôme Petazzoni
jerome.petazz...@dotcloud.com mailto:jerome.petazz...@dotcloud.com
wrote:
If that happens, just try to terminate the other processes running
in the cgroup, rename it (mv /cgroup/mylittlecontainer
Quoting Verdi March (cincaipat...@gmx.net):
...
ifconfig br0 198.55.32.143 promisc up
...
That all looks fine... The fact that it works fine when logging in
from another machine but fails from the host itself must be relevant,
but how...
So your LAN is 198.55.32.X, and your containers are on
