Quoting Stéphane Graber (stgra...@ubuntu.com):
On Mon, Nov 04, 2013 at 02:44:44PM -0600, Serge Hallyn wrote:
So we don't always have to give full paths.
realpath(x,NULL) mallocs memory, but these paths shouldn't get called
from the API so not freeing should be ok.
What's the reason
So we don't always have to give full paths.
realpath(x,NULL) mallocs memory, but these paths shouldn't get called
from the API so not freeing should be ok.
Signed-off-by: Serge Hallyn serge.hal...@ubuntu.com
---
src/lxc/arguments.c | 9 -
src/lxc/lxc_execute.c | 10 +++---
On Mon, Nov 04, 2013 at 02:44:44PM -0600, Serge Hallyn wrote:
So we don't always have to give full paths.
realpath(x,NULL) mallocs memory, but these paths shouldn't get called
from the API so not freeing should be ok.
What's the reason behind this change?
Am I reading this right that this
