On 10/18/2015 7:10 PM, Serge Hallyn wrote:
Quoting Shi, Yang (yang@linaro.org):
On 10/15/2015 7:31 AM, Serge Hallyn wrote:
Quoting Yang Shi (yang@linaro.org):
When run the below command:
lxc-start -n name -f /path/to/config
If config is not a regular file, lxc-start will be killed by
Quoting Shi, Yang (yang@linaro.org):
> On 10/15/2015 7:31 AM, Serge Hallyn wrote:
> >Quoting Yang Shi (yang@linaro.org):
> >>When run the below command:
> >>lxc-start -n name -f /path/to/config
> >>
> >>If config is not a regular file, lxc-start will be killed by SEG FAULT
> >>directly.
> >
When run the below command:
lxc-start -n name -f /path/to/config
If config is not a regular file, lxc-start will be killed by SEG FAULT
directly.
Exit with some error message to improve user experience.
Signed-off-by: Yang Shi
---
src/lxc/lxc_start.c | 13 +
1 file changed, 13 inse
On 10/15/2015 7:31 AM, Serge Hallyn wrote:
Quoting Yang Shi (yang@linaro.org):
When run the below command:
lxc-start -n name -f /path/to/config
If config is not a regular file, lxc-start will be killed by SEG FAULT
directly.
What exactly was the file to get a segfault? When I try with a
Quoting Yang Shi (yang@linaro.org):
> When run the below command:
> lxc-start -n name -f /path/to/config
>
> If config is not a regular file, lxc-start will be killed by SEG FAULT
> directly.
What exactly was the file to get a segfault? When I try with a device
or a directory I do not get a
When run the below command:
lxc-start -n name -f /path/to/config
If config is not a regular file, lxc-start will be killed by SEG FAULT
directly.
Exit with some error message to improve user experience.
Signed-off-by: Yang Shi
---
src/lxc/lxc_start.c | 13 +
1 file changed, 13 inse
