Oh, I also did: mkdir /usr/local/var/lib/misc/
Yes, I tested it on both, lxc-2.0.0.beta2 and lxc-1.1.5
On Thu, Feb 11, 2016 at 12:32 AM, Johannes Kastl <m...@ojkastl.de> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> Am 08.02.16 schrieb Nehal J Wani
gQ/xETbJgYgCeLQOSA+aPskXGPSmx9G3xiIhR
> fMUAniYuKDN2TH7jDUTKz3AdhLs9e7qv
> =GPnA
> -END PGP SIGNATURE-
> ___
> lxc-devel mailing list
> lxc-devel@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-devel
--
Nehal J Wani
__
Signed-off-by: Nehal J Wani <nehaljw.k...@gmail.com>
---
lxcfs.c | 118 ++--
1 file changed, 116 insertions(+), 2 deletions(-)
diff --git a/lxcfs.c b/lxcfs.c
index a561882..9c52862 100644
--- a/lxcfs.c
+++ b/lxcfs.c
@@ -43,6
pts to fix this by assuming that the when no limit is
specified, the value is same that as of cgroup /
Signed-off-by: Nehal J Wani <nehaljw.k...@gmail.com>
---
lxcfs.c | 30 --
1 file changed, 20 insertions(+), 10 deletions(-)
diff --git a/lxcfs.c b/lxcfs.c
inde
When no limit is specified using lxc.cgroup.memory.memsw.limit_in_bytes,
overflow occurs while calculating Swap{Total,Free}. Commit a2de34b tried
to fix this, but introduced another bug, wherein if
memory.memsw.limit_in_bytes >= memory.limit_in_bytes, then Swap{Total,Free}
are not shown as
to
9223372036854775807 (LONG_MAX) in case of CentOS7 (kernel 3.10.0) and
9223372036854771712 in case of Ubuntu14.04 (kernel 4.2.0). So
assumption of LONG_MAX always is obviously wrong.
Only if somehow lxcfs knew that memsw.limit is not set in the
container configuration...?
--
Nehal J Wani
4.3/mm/memcontrol.c#L2893
https://github.com/torvalds/linux/blob/v4.3/include/linux/page_counter.h#L21
Fixes #60
Signed-off-by: Nehal J Wani <nehaljw.k...@gmail.com>
---
lxcfs.c | 23 +++
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/lxcfs.c b/lxcf
