Quoting S.Çağlar Onur (cag...@10ur.org): > Hi, > > It looks like LXC@staging started to write template outputs to stdout like > following when one uses the API; > > [caglar@oOo:~/go/src/github.com/caglar10ur/lxc/examples] sudo ./create > Creating container... > Checking cache download in /var/cache/lxc/raring/rootfs-amd64 ... > Copy /var/cache/lxc/raring/rootfs-amd64 to > /usr/lib/x86_64-linux-gnu/lxc/rootfs ... > Copying rootfs to /usr/lib/x86_64-linux-gnu/lxc/rootfs ... > Generating locales... > en_US.UTF-8... up-to-date > Generation complete. > Creating SSH2 RSA key; this may take some time ... > Creating SSH2 DSA key; this may take some time ... > Creating SSH2 ECDSA key; this may take some time ... > > ## > # The default user is 'ubuntu' with password 'ubuntu'! > # Use the 'sudo' command to run tasks as root in the container. > ## > > It wasn't like that @0.9 and I'm not sure whether this change was > intentional. Wanted to check with you before diving into code to see what > changed.
It was intentional. The template scripts provide meaningful output which I (after switching to lxc_create.c) was silencing, so I considered that a bug. Do you disagree? Should we keep it silent? Should we add an option to lxc-create to dump template output either to a file or stdout or (if unspecified) silent? -serge ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
