You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Been looking at this and it's prohibitively difficult — the child is in a separate process, a black box, so you can't change properties like process.title on it.
Unless there's an API that Workerpool provides to specify the name to the child, I don't think there's a way to do it — and at that point, the child might as well decide its own name, so I don't see the point. The other thing I was thinking was Workerpool could spawn its own intermediary script which itself spawns the worker scripts, but that sounds like bloat to me.
As long as users provide specific worker scripts to Workerpool separate to the entry, then you have control.
Wouldn't it be possible to use message passing to the worker which then in turn sets its own process.title? by default the WorkderPool could give them some default naming like "workerpool-child-3" or something. I guess the main purpose is to make the childs recognizable?
Is there a way of specifying the name of the child processes spawned by the pool? I want them to have different titles from the parent process.
The text was updated successfully, but these errors were encountered: