forwarding to the list because I forgot to use reply-to-all - sorry.
--- Begin Message ---
>> If we want to have a back-channel, we'd need a socket, which makes just
>> doing echo RUNNING > /dev/lxc-notify impossible, you'd need a special
>> program for that. Having the template scripts dump an ad
On 12-09-13 05:26 PM, Christian Seiler wrote:
>> I like the idea but haven't looked at the implementation yet as the
>> patch is really quite large. Quickly scanning through I briefly noticed
>> that the copyright headers for the new files are wrong (refer to IBM and
>> Daniel instead of Christian)
> I like the idea but haven't looked at the implementation yet as the
> patch is really quite large. Quickly scanning through I briefly noticed
> that the copyright headers for the new files are wrong (refer to IBM and
> Daniel instead of Christian).
I just copy&pasted them from the other files, m
On 12-09-13 03:18 PM, Serge Hallyn wrote:
> Quoting Christian Seiler (christ...@iwakd.de):
>> This patch adds a simple notification system that allows the container to
>> notify the host (in particular, the lxc-start process) that the boot process
>> has been completed successfully. It also adds an
Quoting Christian Seiler (christ...@iwakd.de):
> This patch adds a simple notification system that allows the container to
> notify the host (in particular, the lxc-start process) that the boot process
> has been completed successfully. It also adds an additional status BOOTING
> that lxc-info may
This patch adds a simple notification system that allows the container to
notify the host (in particular, the lxc-start process) that the boot process
has been completed successfully. It also adds an additional status BOOTING
that lxc-info may return. This allows the administrator and scripts to
di
