From: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: Sukadev Bhattiprolu
<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org,
Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [PATCH 1/1] lxc-ps: Nit - Avoid blank CONTAINER column
Date: Fri, 12 Feb 2010 18:01:28 +0100 [thread overview]
Message-ID: <4B758968.30800@fr.ibm.com> (raw)
In-Reply-To: <20100211042531.GA8835-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
On 02/11/2010 05:25 AM, Sukadev Bhattiprolu wrote:
> From: Sukadev Bhattiprolu<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> Date: Wed, 10 Feb 2010 20:09:17 -0800
> Subject: [PATCH 1/1] lxc-ps: Nit - Avoid blank CONTAINER column
>
> The contianer name is not printed in the lxc-ps output unless the --lxc
> option is specified. But the CONTAINER column is printed (and left
> blank) even if the --lxc option is not specified.
>
> $ /usr/local/bin/lxc-ps -n foo
> CONTAINER PID TTY TIME CMD
> 19525 pts/2 00:00:01 bash
> 20311 pts/2 00:00:00 lxc-ps
> 20312 pts/2 00:00:00 ps
>
> Like normal ps, it would be less confusing (IMHO) if the CONTAINER
> column is skipped unless the --lxc option is specified.
>
> $ ./lxc-ps -n foo
> PID TTY TIME CMD
> 19525 pts/2 00:00:01 bash
> 20339 pts/2 00:00:00 lxc-ps
> 20340 pts/2 00:00:00 ps
>
> $ ./lxc-ps --lxc -n foo
> CONTAINER PID TTY TIME CMD
> foo 19646 pts/1 00:00:00 lxc-init
> foo 19647 pts/1 00:00:00 bash
it would be real nice to have but without the --lxc.
can we kill the short option '-n', which conflicts with the ps below, and make
sure that only '--name' triggers the extra CONTAINER column ?
C.
prev parent reply other threads:[~2010-02-12 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 4:25 [PATCH 1/1] lxc-ps: Nit - Avoid blank CONTAINER column Sukadev Bhattiprolu
[not found] ` <20100211042531.GA8835-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-11 10:08 ` Michel Normand
2010-02-11 10:21 ` [lxc-devel] " Michel Normand
[not found] ` <1265883662.2591.68.camel@pagloppaglop>
2010-02-11 15:54 ` Serge E. Hallyn
[not found] ` <20100211155446.GC6884@us.ibm.com>
[not found] ` <20100211155446.GC6884-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-11 18:19 ` Sukadev Bhattiprolu
[not found] ` <20100211181902.GA3742-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-12 7:48 ` Michel Normand
2010-02-12 16:54 ` Cedric Le Goater
2010-02-12 17:01 ` Cedric Le Goater [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B758968.30800@fr.ibm.com \
--to=clg-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox