From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Christopher Larson <clarson@kergoth.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] bitbake: Set process names to be meaninful
Date: Sun, 31 Jan 2016 17:54:04 +0000 [thread overview]
Message-ID: <1454262844.27087.30.camel@linuxfoundation.org> (raw)
In-Reply-To: <CABcZAN=+4HozZSOcHEC0yD_5j3w9C=SEwyz1RpT_W12Htj1OiQ@mail.gmail.com>
On Sun, 2016-01-31 at 10:03 -0700, Christopher Larson wrote:
> On Fri, Jan 29, 2016 at 4:08 AM, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> > This means that when you view the process tree, the processes
> > have meaningful names, aiding debugging:
> >
> > Applies to parse threads, PR Server, cooker, the workers and
> > execution
> > threads, working within the 16 character limit as best we can.
> >
> > Needed to tweak the bitbake-worker magic values to tell the
> > workers apart.
> >
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> >
> This is nice, but shouldn't we at least include 'bitbake' somewhere
> in the process names? Will this interfere with the ability to use
> pkill/killall to kill bitbake processes in cases where it's
> necessary?
I thought I'd checked this and that killall was working off the output
in ps which was based off argv[0] and was unchanged. Checking again
just now shows that isn't correct.
I guess the question is where to include "bitbake". We're short of
space already for the worker processes for example. Perhaps if we just
included bitbake for the cooker and UI?
Cheers,
Richard
prev parent reply other threads:[~2016-01-31 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 11:08 [PATCH] bitbake: Set process names to be meaninful Richard Purdie
2016-01-31 17:03 ` Christopher Larson
2016-01-31 17:54 ` Richard Purdie [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=1454262844.27087.30.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.