On 1/28/11 10:11 PM, jida...@jidanni.org wrote: > I isolated the problem and submitted > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611417 which I forget > to X-Debbugs-cc to bash-...@gnu.org, which I should have, as it probably > is a upstream problem that only the bash authors can fix.
Is it a problem? Bash prints messages about signal-terminated processes -- at least those that don't die due to SIGINT or SIGPIPE -- when the shell is not interactive. Most people want to know when their jobs die and their scripts fail. (And, by the way, historical versions of sh did the same thing.) Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/