Stefano Lattarini wrote:
> Hi everybody.
> I found the following bug while running some of my bash scripts on 
> GNU/Linux with stdout redirected to /dev/full, to see if write errors
> where correctly detected and reported.
> It turned out that, on write errors, the printf builtin correctly
> returns a non-zero status (thus my scripts at least had a correct
> exit status), but unfortunately it does not always display a suitable
> error message on stderr; in particular, it fails to do so if the
> printed  string does *not* end with a newline. 

Thanks for the report.  This will be fixed in the next version.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU

Reply via email to