qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Allow setting qemu process name
Date: Wed, 1 Jul 2009 17:27:10 +0100	[thread overview]
Message-ID: <20090701162710.GB4555@shareable.org> (raw)
In-Reply-To: <20090701140644.GV6760@one.firstfloor.org>

Andi Kleen wrote:
> On Wed, Jul 01, 2009 at 08:57:47AM -0500, Anthony Liguori wrote:
> > Andi Kleen wrote:
> > >On Wed, Jul 01, 2009 at 08:29:22AM -0500, Anthony Liguori wrote:
> > >  
> > >It's only default with -name. I don't think anyone would look through
> > >/proc matching for process names, that would be too broken anyways.
> > >If they look through ps ax they would still work.
> > >  
> > 
> > If someone has a script today that uses top -n 1 | grep 
> > qemu-system-x86_64 that script will break.
> 
> That would already break if qemu-system-x86_64 is by chance not in 
> the ~20 or so processes that take the most CPU time. That is what I meant
> with already broken. I consider it very likely that the scripts
> all use ps at least, which is not affected.

These's also ps's "c" option:

    "Show the true command name. This is derived from the name of the
    executable file, rather than from the argv value. Command
    arguments and any modifications to them (see setproctitle(3)) are
    thus not shown."

Looks liks Linux has 3 different command names to choose from:

    - argv[0]
    - PR_SET_NAME
    - Name derived from /proc/self/exe

-- Jamie

  parent reply	other threads:[~2009-07-01 16:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01  9:32 [Qemu-devel] [PATCH] Allow setting qemu process name Andi Kleen
2009-07-01 13:29 ` Anthony Liguori
2009-07-01 13:43   ` Andi Kleen
2009-07-01 13:57     ` Anthony Liguori
2009-07-01 14:06       ` Andi Kleen
2009-07-01 15:08         ` Avi Kivity
2009-07-01 16:27         ` Jamie Lokier [this message]
2009-07-01 15:07   ` Avi Kivity
2009-07-01 16:19     ` Luiz Capitulino
2009-07-01 16:27       ` Avi Kivity
2009-07-01 16:34         ` Luiz Capitulino
2009-07-01 16:43           ` Avi Kivity
2009-07-01 17:02             ` Jamie Lokier
2009-07-01 17:43     ` Stefan Weil
2009-07-23 11:47 ` Todd T. Fries
2009-07-23 12:01   ` Andi Kleen
2009-07-23 12:58     ` Todd T. Fries
2009-07-23 14:30       ` Andi Kleen
2009-07-24  9:34   ` Richard W.M. Jones

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=20090701162710.GB4555@shareable.org \
    --to=jamie@shareable.org \
    --cc=andi@firstfloor.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).