Quoting Dwight Engen (dwight.en...@oracle.com):
> Signed-off-by: Dwight Engen
Acked-by: Serge E. Hallyn
> ---
> doc/lxc-info.sgml.in | 28 +---
> src/lxc/lxc_info.c | 27 ---
> 2 files changed, 49 insertions(+), 6 deletions(-)
>
> diff --git a
Quoting Dwight Engen (dwight.en...@oracle.com):
> commit 829dd918 added parsing of a -c argument to both the common options
> handling and to lxc-start. It is not a common option, and should have only
> been added to lxc-start. Because the common code is processing it, no other
> command can use -c
Signed-off-by: Dwight Engen
---
doc/lxc-info.sgml.in | 28 +---
src/lxc/lxc_info.c | 27 ---
2 files changed, 49 insertions(+), 6 deletions(-)
diff --git a/doc/lxc-info.sgml.in b/doc/lxc-info.sgml.in
index ba0a044..39cd4d1 100644
--- a/doc/lxc-in
commit 829dd918 added parsing of a -c argument to both the common options
handling and to lxc-start. It is not a common option, and should have only
been added to lxc-start. Because the common code is processing it, no other
command can use -c. Remove -c from being processed by the common code.
Tes
Quoting lsmushroom (lsmushr...@126.com):
> Sorry for the late response. For your question , you could not limit
> the network traffic in that way. Because TC will only limit the
But it worked for me...
Are you saying it will limit only traffic to, but not from, the
container?
> traffic send out
Sorry for the late response. For your question , you could not limit the
network traffic in that way. Because TC will only limit the traffic send out
from the target device . And for the device of veth type , the device on the
host end will “send out” the traffic to the container , and it will
