Reidrect stderr of child process



I have inherited the maintenance of a client app and the associated server.
Simply, the server waits for the client to trigger it; when triggered, the
server runs a child proces, and sends output back to the client.
I an having trouble re-directiong the output from the server to the client.

I found this in the server code:
// The steps for redirecting child process's STDERR:
// 1. Save current STDERR, to be restored later.
// 2. Create anonymous pipe to be STDERR for child process.
// 3. Set STDERR of the parent to be the read handle to the
// pipe, so it is inherited by the child process.
// 4. Create a noninheritable duplicate of the write handle,
// and close the inheritable write handle.

Does that make sense? Is it true for stdout as well as stderr?
When the client triggers the server, it looks like stdout is re-directed,
but not stderr.

Thanks for any help.



.



Relevant Pages

  • RE: call to xp_cmdshell from trigger problem
    ... Open query analyzer and connect to the server with Windows Authentication ... try a test and see if the client gets the required info. ... > At first it failed because the trigger called the EXE but the tables were ...
    (microsoft.public.sqlserver.server)
  • Re: select + stderr
    ... What means stdout in the context of a server-client pair? ... >>file), I get the error message on server side on stderr, but on client ...
    (comp.unix.programmer)
  • Re: select + stderr
    ... > I have a client - server, but this works only for stdout. ... > file), I get the error message on server side on stderr, but on client ...
    (comp.unix.programmer)
  • Re: How could I directly trigger a very simple on localhost and a known port listening server from m
    ... > little server would be running on the client machine, where my browser ... > side would be to trigger a scanner, ...
    (comp.lang.javascript)
  • Re: Displaying Error Messages From Triggers
    ... I find RAISERROR messages from SQL Server are consistently reported in client ADPs in both Access 2002 and Access 2003 but ONLY if ... In my post below I described a problem I have been experiencing since the client upgraded to Access 2003. ... If I can't get the trigger to raise errors, what is the best work around? ... I would like to leave the business logic on the server ...
    (microsoft.public.access.adp.sqlserver)

Loading