Mikhail Gusarov wrote: > Hi. > > I have tried to run lxc tools from git and got the following output: > > [dotted...@vertex:~]% sudo lxc-start --logfile=/dev/stderr > --logpriority=TRACE -n cf > lxc-start 1270236851.229 INFO lxc_conf - tty's configured > lxc-start 1270236851.229 ERROR lxc_console - Bad address - failed to > open '(null)' > lxc-start: Bad address - failed to open '(null)' > lxc-start 1270236851.229 ERROR lxc_start - failed to create console > lxc-start: failed to create console > lxc-start 1270236851.229 ERROR lxc_start - failed to initialize the > container > lxc-start: failed to initialize the container > > According to source, console->path is ever initalized to non-NULL if > there is lxc.console option in config file. If lxc.console is mandatory > now it could be cool to handle it in a bit more clear way. > Argh! no, it's not mandatory, it's a regression.
Thanks for reporting the problem. I think it is fixed, please git pull. Let me know if that works now. -- Daniel ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
