jobs in scripts?

[Dan Muresan <danmbox@xxxxxxxxx>]

Hi, is the following normal? With set -m the problem disappears; bash
& ksh don't need set -m.

SUSv3 doesn't say job control is to be disabled completely unless "set
-m" is active. And, if job control *is* disabled, why does "job"
report a non-empty list?

0.5.5.1-3ubuntu2 on Ubuntu 10.04 here.

---

$ cat x
#set -m
sleep 100 &
echo "Before kill:"; jobs -l
kill -s TERM %1
sleep 0.5
echo "After kill:"; jobs -l
pidof sleep



$ dash x
Before kill:
[1] + 18775 Running
kill: 4: No such process

After kill:
[1] + 18775 Running
18775


-- Dan
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html