in reply to Redirecting STDOUT
in thread Redirecting STDOUT
its a client server app
we have an application (sqr) that can only run (licensing issues) on one machine. Currently we rsh commands over to that box. This has been ok for many years but now we have run up against resource issues with that box. Our unix sa says that there is a limit on the number or rsh sessions that it can handle. So , we decided to rewrite the process using a socket client forking-server set of programs. What I found out while doing this is that many programmers have left alot of debug 'show' commands in their sqr code. For debuging and testing of this new process it was necessary for me to be able to not have all the clutter of these 'debug' statments spewing into the stdout of the server (the parent process).