<div dir="ltr"><div class="gmail_extra">On Wed, Jan 6, 2016 at 9:25 AM, Ross Burton <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":ux" class="a3s" style="overflow:hidden">If the setproctitle module is present then use it to change the process name<br>
when the worker starts a task. This results in each worker showing what task it<br>
is executing in a process listing.<br>
<br>
Signed-off-by: Ross Burton <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>></div></blockquote></div><br></div><div class="gmail_extra">Very nice. Do you know if it's overwriting just the process name or the entire commandline? I'm wondering if pkill bitbake-worker would do what you want, or if you'd still need to use pkill -f, for example. I'd like to see the toplevel bitbake processes named nicely without the python path and whatnot too eventually. We could also name the parallel parsing processes (though admittedly they're not long lived). Perhaps this should go into a helper function in bb.utils or bb.process?<br>-- <br><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>