On Mon, 11 Dec 2000, Gilles Detillieux wrote:
> stdin and stderr at all??? If you close stdin, you should probably
> reopen is with /dev/null or something inoccuous like that, or perhaps
> better yet the input file itself. However, a properly written external
> parser or converter should simply leave stdin alone.
Yes, my thoughts exactly. But I also didn't like the caveat of
"properly-written." Setting stdin to /dev/null or the contents of the
input file itself seem like decent alternatives.
> In any case, you most definitely DO NOT want to close stderr, or you
> lose any error output from the external parser or converter, which
> would be disatrous in terms of trying to debug its operation. The
> popen didn't do this, so why are we doing it now?
Good point.
> By the way, the customary practise when fork() fails is to sleep a few
> seconds and try again, up to a certain maximum (2-4 times), or just give
Look, I've written about zero code using fork, popen, dup, and company. So
I don't know the "customs" about using them. Yes, I can read the man
pages, but that's not the same as experience.
I'd be quite happy to concentrate on the stuff I *do* have experience
doing (i.e. htsearch work, system architecture and planning) But it also
seems like there are a lot of important lower-level things that no one is
stepping forward to do.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
