zsh-users
 help / color / mirror / code / Atom feed
* job control in a script / zsh parallelism problem.
@ 2012-03-15 11:25 Simon Mages
  2012-03-16 20:29 ` Peter Stephenson
  0 siblings, 1 reply; 2+ messages in thread
From: Simon Mages @ 2012-03-15 11:25 UTC (permalink / raw)
  To: zsh-users

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

Hi,

i have some Problems with the job control in zsh.

In the following Script i tried to start 3 background processes, because
thats the only way i know to run things parallel in zsh, and write a "dot"
every two seconds during the runtime of this background Processes.

#!/usr/bin/zsh

#set -x

for i in a b c
do
 sleep 120 &
done

jobs -l

jobs -l |wc -l

var=`jobs -l|wc -l`

while [ $var -gt "0" ]
do
 print "."
 sleep 2
 var=`jobs -l|wc -l`
done

The Problem is that "jobs -l" in the Script writes an complete background
process list to stdout but "jobs -l|wc -l" just prints a "0"? When i run
"jobs -l|wc -l" manual with some background jobs it is working fine.

Can someone Point me i the right direction, i'm running out of useful ideas.

Here the Output of the Script without set -x:

#> ./test.sh
[2] 4916 running sleep 120
[3] - 1716 running sleep 120
[4] + 4160 running sleep 120
0

here with set -x:

#> ./test.sh
+./test.sh:5> i=a
+./test.sh:5> i=b
+./test.sh:7> sleep 120
+./test.sh:7> sleep 120
+./test.sh:5> i=c
+./test.sh:10> jobs -l
[2] 3532 running sleep 120
[3] - 1600 running sleep 120
[4] + 5292 running sleep 120
+./test.sh:7> sleep 120
+./test.sh:12> jobs -l
+./test.sh:12> wc -l
0
+./test.sh:14> var=+./test.sh:14> var=+./test.sh:14> jobs -l
+./test.sh:14> wc -l
+./test.sh:14> var=0
+./test.sh:16> [ 0 -gt 0 ']'


My test environment:

#> zsh --version
zsh 4.3.12 (i686-pc-cygwin)


BR Simon

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: job control in a script / zsh parallelism problem.
  2012-03-15 11:25 job control in a script / zsh parallelism problem Simon Mages
@ 2012-03-16 20:29 ` Peter Stephenson
  0 siblings, 0 replies; 2+ messages in thread
From: Peter Stephenson @ 2012-03-16 20:29 UTC (permalink / raw)
  To: zsh-users

On Thu, 15 Mar 2012 12:25:18 +0100
Simon Mages <mages.simon@googlemail.com> wrote:
> In the following Script i tried to start 3 background processes, because
> thats the only way i know to run things parallel in zsh, and write a "dot"
> every two seconds during the runtime of this background Processes.
> 
> #!/usr/bin/zsh
> 
> #set -x
> 
> for i in a b c
> do
>  sleep 120 &
> done
> 
> jobs -l
> 
> jobs -l |wc -l
> 
> var=`jobs -l|wc -l`
> 
> while [ $var -gt "0" ]
> do
>  print "."
>  sleep 2
>  var=`jobs -l|wc -l`
> done
> 
> The Problem is that "jobs -l" in the Script writes an complete background
> process list to stdout but "jobs -l|wc -l" just prints a "0"? When i run
> "jobs -l|wc -l" manual with some background jobs it is working fine.

First answer: what's going on here.  (I think you'll like the second
answer better, however.)

Normally, you don't get full job control in a non-interactive shell,
only the basic features.  When you run "jobs" at the start of a
pipeline, it's in a subshell; there aren't any running processes in that
subshell, so the shell reports nothing.

In interactive shells, the shell option MONITOR is set, which gives you
full job control.  In this case, the shell does a little extra for you:
it saves the job table when you enter a subshell and uses it if there
are no jobs in the subshell.

If you have a recent version of the shell you can set the MONITOR option
in a non-interactive shell.  You can do that just by putting "-m" after
the "#!/usr/bin/zsh".  If the shell's too old, you'll get an error when
it tries to turn on job control.

Note that, because this uses full job control, you get more verbose
output than from starting background jobs in a normal script.

Behind this is the fact that the "jobs" command was really originally
designed for giving information to the user in interactive shells.


Second answer: a better way.

It's actually possible to use special parameters to examine the
job states, and although this is specific to zsh it's much neater.
See the zshmodules manual page and look for the zsh/parameter module,
which has various parameters whose names begin with "job".

Here's a slightly truncated version of your script testing the length of
the $jobstates array that worked fine for me.


#!/usr/bin/zsh

zmodload zsh/parameter

for i in a b c
do
 sleep 120 &
done

while (( ${#jobstates} ))
do
 print "."
 sleep 2
done


-- 
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-03-16 20:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-03-15 11:25 job control in a script / zsh parallelism problem Simon Mages
2012-03-16 20:29 ` Peter Stephenson

Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).