Re: [Bug-wget] Strange wget behavior when saving to stdout

[Giuseppe Scrivano]

Micah Cowan <address@hidden> writes:

> The error message it's reporting seems to correspond to ENOENT
> instead... wonder if it's mistakenly getting that error from normal
> gettext() lookups, rather than any messages actually related to the
> close... the actual close(1) from the strace log in my first message,
> seems to have returned 0. If that's the case, shame on them! ;) errno
> shouldn't generally be considered meaningful unless it's set to 0 just
> prior to the call, and checked immediately after a verified-failed call.

I have removed the gnulib module.  I don't think it is a big loss, when
-O is specified the stream is flushed immediately when some data is
received.

The problem was that "close(1)" was called twice, once by "cleanup" and
the second time by "close_stdout" by the "atexit" registered hook.

Maybe we should use a wrapper around it that checks if the file is still
opened before call close_stdout?  But I think this can wait after the
release though :-)

Giuseppe