On Sun, Jan 23, 2011 at 10:06:40PM +0800, jida...@jidanni.org wrote:
> Gentlemen, I am disturbed by these seemingly irregular results,
> # perl -pwle 's/\d{4}//' mm|sort|uniq -c
> 88 ++ kill
Huh? Speak clearly.
> from running my program
> # cat rt
> set -x
> set -m
> sleep 33&
> ki
Thanks Greg, but aren't I acting by the rules?
$ cat l
set +m
sleep 44&
kill $!
$ for i in `seq 33`; do bash -xm l; done
Which gives
+ kill 5256
+ set +m
+ kill 5258
+ set +m
+ kill 5260
l: line 4: 5260 Terminated sleep 44
+ set +m
+ kill 5262
+ set +m
+ kill 5264
+ set +m
I.e., one
On Mon, Jan 24, 2011 at 10:46:03PM +0800, jida...@jidanni.org wrote:
> Thanks Greg, but aren't I acting by the rules?
I don't know. I've never before seen anyone flip monitor mode on and off
like a toddler that just discovered a light switch.
imadev:~$ cat normal
#!/bin/sh
sleep 20 &
kill $!
im
Hi,
I'm using Bash's $RANDOM variable to create repeatable sequences of
pseudo-random numbers. I used seeds >= 0, and noticed random
non-repeatable sequences for RANDOM=0, which I didn't expect given the
documentation.
Looking at the code, it appears that RANDOM=0 has a specific value,
which appe
> "GW" == Greg Wooledge 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.
On 1/23/11 10:53 PM, Olivier Mehani wrote:
> Hi,
>
> I'm using Bash's $RANDOM variable to create repeatable sequences of
> pseudo-random numbers. I used seeds >= 0, and noticed random
> non-repeatable sequences for RANDOM=0, which I didn't expect given the
> documentation.
>
> Looking at the code
