(I hit the wrong reply button, and my response just went to Bill - resending again)
>-----Original Message----- >From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED] > >At 11:21 AM 6/5/2003, MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: > >>Well.. in that case, I'd suppose it's better to dup stderr to >/dev/null >>(even better - the apache error_log) rather than closing >stderr. If the >>intention is to avoid children from writing to stderr, we >ought to dup it so >>that we know when a *real* error message is being printed. > >That is what Apache has traditionally done (at least in 1.3 >and I believe >in 2.0 as well.) Well..Is that an good enough excuse to continue doing it in Apache 2.x also ? .. or should we aim towards correctness ?. If an application is closing stderr and not handling the error conditions OR expecting that nothing be written to stderr, then I'd say the application is wrong.. One cannot make such assumptions, as there was a particular reason why stderr was designed. If ppl don't want to see the message being printed on the screen,they should handle it in the application, and not 'assume' things about the underlying libraries.. -Madhu
