Home/ Questions/Q 3214176
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T15:01:46+00:00

Let’s say I have 10 programs (in terminals) working in tandem: {p1,p2,p3,…,p10}. It’s hard

  • 0

Let’s say I have 10 programs (in terminals) working in tandem: {p1,p2,p3,…,p10}.

It’s hard to keep track of all STDOUT debug statements in their respective terminal. I plan to create a GUI to keep track of each STDOUT such that, if I do:

— Click on p1 would “tail” program 1’s output.
— Click on p3 would “tail” program 4’s output.

It’s a decent approach but there may be better ideas out there? It’s just overwhelming to have 10 terminals; I’d rather have 1 super terminal that keeps track of this.

And unfortunately, linux “screen” is not an option. RESTRICTIONS: I only have the ability to either: redirect STDOUT to a file. (or read directly from STDOUT).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you are looking for a creative alternative, I would suggest that you look at sockets.

    If each program writes to the socket (rather than STDOUT), then your master terminal can act as a server and organize the output.

    Now from what you described, it seems as though you are relatively constrained to STDOUT, however it could be possible to do something like this:

    # (use netcat (or nc on some systems) to write to a socket on the provided port)
./prog1 | netcat localhost 12312

    I’m not sure if this fits in the requirements of what you are doing (and it might be more effort than it is worth!), but it could provide a very stable solution.

    EDIT: As was pointed out in the comments, netcat does exactly what you would need to make this work.

    • 0