Hi Gary, [Gary V. Vaughan] > Unless compiled specially just to avoid it, bash gives an occasional > disconcerting (but spurious) warning when a process at the receiving > side of a shell pipe closes before the sender has flushed all of its > data.
I consider this to be a bug in bash. Half of the major Linux distributions do patch the bash they package to prevent this problem, so I am not alone. > `quilt refresh' is particularly prone. True, but there are several other cases where the case can trigger. > This patch simply redirects stderr to /dev/null in the one instance > that seems to be the root of the problem, and thus saves the bother > of recompiling bash. Redirecting stderr to /dev/null is not an acceptable solution, sorry. See my post on this topic 4 months ago: http://lists.gnu.org/archive/html/quilt-dev/2005-05/msg00031.html It got no answer unfortunately. The only thing we can do is probably to document the problem, and ask remaining distributions (Linux or not) to apply the patch fixing the problem when building their bash package. Maybe then the bash folks will finally agree that this should be made the default. Thanks, -- Jean Delvare _______________________________________________ Quilt-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/quilt-dev
