BAT job hangs on hidden "Terminate batch job (Y/N)?"

[panreyes]

I copied serviceui.exe in C:\ and used this script to launch cmd.exe as SYSTEM but making it available in the user session at the same time.

C:\serviceui.exe -process:explorer.exe "c:\windows\system32\cmd.exe"

But it hanged up and the agent wasn't able to complete the job. (And it even triggered the job again every few minutes, I don't know why.

By running the generated bat file, I noticed that if I closed cmd.exe with the X instead of the exit command, this would be shown:

Terminate batch job (Y/N)?

To make it work correctly, I did a small change in modules_meshcore/scripttask.js.

From this:

child.stdin.write(pName + ' > ' + oName + '\r\n');

To this:

child.stdin.write('echo n | ' + pName + ' > ' + oName + '\r\n');

It's not the most ellegant solution, but it seems to be currently working for me :)

[ryanblenis]

It runs every few minutes because it is trying to complete the script run you assigned to it. The question is, what is the script trying to do and why is it hanging instead of returning at that point? You'll probably want to handle that inside the script versus piping an input to [presumably] every script that runs.

[panreyes]

Thank you for your response @ryanblenis , I'm glad to see that this plugin is not abandoned :)

I don't know the reason, but the command line I mentioned in my previous message (C:\serviceui.exe -process:explorer.exe "c:\windows\system32\cmd.exe") does block the process with a Terminate batch job (Y/N) message, and the echo n | solved it in that case, but I have already noticed that this solution does not work for every script.

On the other side, I think I dont understand the flow of running the scripts.
I don't see the point of running the script again until it completes successfully.

For example, a BAT script with just this line:

ping -n 1000 8.8.8.8

will start spawning multiple pings instead of waiting for the current one to complete.
In the Node history I only see one job/script "Running",

For what I can see, the "Time" is updated to the latest execution.

But ScriptTask has triggered the job multiple times:

I just pressed the "Run" button once in one script that I expected to send 1000 pings to 8.8.8.8 and complete.

BTW: I'm using latest MeshCentral, with classic UI and NeDB.