The exec node PID is propagated via the status node in the status.text property, however, there is no context, other than the originating exec node. When executing different types of commands (and i mean a lot of them), there is no way to keep track which PID is responsible for which process. Would…

Indeed by default I think i don't need the pid (although it still wouldn't hurt, in case it hangs somewhere), but I was referring to the spawn mode.

In spawn mode it still wouldn’t appear until the command sends something. Would that be ok ?

I think so yes, that would be great. I will use a different property for the actual command, so that the complete command + pid would be/remain available in the msg that can be used as reference.

of course you should be able to add your own msg.property and it should be preserved if you need to track requests.

Node-RED

Node-RED Forum

Tracking exec node spawn PIDs

Core Development Feature Requests

dceejay 28 January 2023 08:48 2

Well it could, but nothing comes out of those outputs until after the command has finished, whereas you may need the pid when it starts if you need to monitor/kill it

Topic		Replies	Views
Elegant way to get pid of exec node running in spawn mode? General	5	2451	11 December 2020
Exec node question General	18	12739	15 October 2018
Status of an Exec node General	2	323	16 September 2022
A conundrum with exec node and kill General	9	2353	23 June 2020
Questions about the EXEC node General	6	96	28 November 2024

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Tracking exec node spawn PIDs

Related topics