>>>>> "GW" == Greg Wooledge <wool...@eeg.ccf.org> writes:
GW> You used seq, so you're clearly doing it on Linux. Maybe it's an
GW> OS-specific thing?
Package: bash
Version: 4.1-3
Debian Release: 6.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bash depends on:
ii base-files 6.0 Debian base system miscellaneous f
ii dash 0.5.6.1-1~exp0 POSIX-compliant shell
ii debianutils 3.4.3 Miscellaneous utilities specific t
ii libc6 2.11.2-9 Embedded GNU C Library: Shared lib
ii libncurses5 5.7+20100313-5 shared libraries for terminal hand
I note it doesn't happen when su'ed to user nobody. Nor when using 'do
sh', nor is it easy to find if one sends it to a pipe. Also it takes
several tries to get. Now adding -p, to exclude any $ENV.
$ cat u
echo $-
set +mbi
sleep 44&
kill $!
$ for i in {1..10}; do bash -xpm u; done
Around run #5 gave
+ set +mbi
+ kill 10471
u: line 5: 10471 Terminated sleep 44
I.e., one out of ten gave the message. Then several more runs of the
above line didn't.
