There is a DVLOG(0) statement in ChildProcessHost::DoLaunch() that used to print out the pid and the service name when launching mustash services. For example, the log statements would include "service:ui" when launching the mus-ws process. The DVLOG is still there but it no longer contains any information about what process is what. The output we get now is below:
[89433:89438:1103/161229:868064789654:INFO:child_process_host.cc(202)] Launched child process pid=89439, instance=c1bd02b0-6b15-4640-9339-72f09b850ebe, name=service:chrome_mash, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[89433:89438:1103/161230:868065242564:INFO:child_process_host.cc(202)] Launched child process pid=89441, instance=8f8986a5-c155-4af4-8338-ddff779c2bff, name=service:chrome_mash, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[89433:89438:1103/161230:868065244925:INFO:child_process_host.cc(202)] Launched child process pid=89442, instance=4dea90a1-0212-4a03-9ad4-193452497821, name=service:chrome_mash, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[89433:89438:1103/161230:868065246325:INFO:child_process_host.cc(202)] Launched child process pid=89443, instance=, name=service:content_browser, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[89433:89438:1103/161230:868065591617:INFO:child_process_host.cc(202)] Launched child process pid=89534, instance=, name=service:tracing, user_id=63a3e132-f802-4f4a-8782-e880028651ea
[89433:89438:1103/161230:868065594615:INFO:child_process_host.cc(202)] Launched child process pid=89537, instance=7bc0bf5b-aea6-45a1-a06c-3ca2b3a50a2f, name=service:chrome_mash, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[89433:89438:1103/161230:868065963593:INFO:child_process_host.cc(202)] Launched child process pid=89663, instance=f62f91e5-f645-4527-a7cf-f25a16559fa0, name=service:chrome_mash, user_id=9b1cd2b0-3261-4853-8b90-cbe92c162449
[89433:89438:1103/161231:868066298876:INFO:child_process_host.cc(202)] Launched child process pid=89674, instance=b380689b-9ebc-4a52-bbd0-13cdf86a010a, name=service:chrome_mash, user_id=9b1cd2b0-3261-4853-8b90-cbe92c162449
Comment 1 by kylec...@chromium.org
, Jun 20 2017