[lxc-devel] template output

[S.Çağlar Onur]

Hi Serge,

On Wed, Jul 10, 2013 at 10:36 AM, Serge Hallyn <serge.hallyn at ubuntu.com>wrote:

> Quoting S.Çağlar Onur (caglar at 10ur.org):
> > Hi,
> >
> > It looks like LXC at staging started to write template outputs to stdout
> like
> > following when one uses the API;
> >
> > [caglar at 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
>

I think your suggestion "providing an option to dump template output either
to a file or stdout or (if unspecified) silent" sounds best among possible
solutions.

Cheers
-- 
S.Çağlar Onur <caglar at 10ur.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20130710/e0d74009/attachment.html>