> Can you file an issue on Github with the details and your suggestions to
>
> track this, please?
Yes, I will try.
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
On Thu, Jul 05, 2018 at 01:06:29PM -0400, Chaetoo3 wrote:
> > You mean it wouldn't change from "my binary --with --args" to "[lxc
> > monitor]?
>
> Yes, exactly like that.
>
> It seems to me that proc stat file is for machine parsing, but is not
> so convenient for machine parsing. I do not kno
> You mean it wouldn't change from "my binary --with --args" to "[lxc monitor]?
Yes, exactly like that.
It seems to me that proc stat file is for machine parsing, but is not so
convenient for machine parsing. I do not know if there is an official
technique. There are some ways, but they all se
On Thu, Jul 05, 2018 at 03:42:55PM +0200, Christian Brauner wrote:
> On Wed, Jul 04, 2018 at 03:23:19PM -0400, Chaetoo3 wrote:
> > Hi!
> >
> > I try to use the liblxc start() API from my process and it worked, but
> > I notice it would not set the process name for the container process
> > as it w
On Wed, Jul 04, 2018 at 03:23:19PM -0400, Chaetoo3 wrote:
> Hi!
>
> I try to use the liblxc start() API from my process and it worked, but
> I notice it would not set the process name for the container process
> as it would do from the lxc-start command line. Instead the container
> process staye
Hi!
I try to use the liblxc start() API from my process and it worked, but I notice
it would not set the process name for the container process as it would do from
the lxc-start command line. Instead the container process stayed with the name
of my caller.
I sniff around and make a local fix.
