How do I link to the STDOUT/STDERR of the "native" ODM from outside?

I’m using the “native” ODM installation under /code in a WSL2 image, hosted by Windows 10.

I use Windows Terminal to link to my WSL2 ODM instance to run jobs via the command-line.

During a particularly long job, my Windows Terminal software was auto-updated, which closed the connection, but left the job running.

How can I link into the STDOUT/STDERR for the running process so that I can see the debug/verbose messages that it should be outputting?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.