[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[RFC] closeout redundant diagnostic
From: |
Pádraig Brady |
Subject: |
[RFC] closeout redundant diagnostic |
Date: |
Tue, 17 May 2011 12:11:06 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 |
I was just testing a framebuffer device here and
noticed that there were 2 errors printed by `tr`
$ tr '\0' $(($RANDOM % 256)) </dev/zero >/dev/full
tr: write error: No space left on device
tr: write error
I was then wondering it there was some other
error with the device rather than just filling it.
But the latter error is just closeout() noticing
the original write error, and diagnosing just
in case the original writer did not.
So 3 options.
1. leave as is
2. assume all writers will diagnose,
so don't diagnose previous errors in closeout()
3. make it configurable (with close_stdout_set_ignore_previous())
I might just leave as is?
cheers,
Pádraig.
- [RFC] closeout redundant diagnostic,
Pádraig Brady <=