Dash double semicolon (;;) syntax

syntax sh dash-shell
valodzka picture valodzka · Jun 3, 2013 · Viewed 23.5k times · Source

I'm tried to find way to run multiple commands in parallel in sh and wait for it completion.

I've found that following doesn't work (sh: 1: Syntax error: ";" unexpected):

sh -c '(sleep 3 && echo 1) & ; (sleep 3 && echo 2) & ;  wait'

But this syntax works as expected:

sh -c '(sleep 3 && echo 1) & ;; (sleep 3 && echo 2) & ;;  wait'

But I don't understand what is the difference.

What is the meaning of ;; and when it should be used?

Answer

Gilles 'SO- stop being evil' picture Gilles 'SO- stop being evil' · Jun 3, 2013

;; is only used in case constructs, to indicate the end of an alternative. (It's present where you have break in C.)

case $answer in
  yes) echo 'yay!';;
  no) echo 'boo!';;
esac

Syntactically, ; and & both mark the end of a command. A newline is equivalent to ;, in a first approximation. The difference between them is that ; or newline indicates that the command must be executed in the foreground, whereas & indicates that the command must be executed in the background.

So here you need & wait. & ; is a syntax error (you can't have an empty command). & ;; is also a syntax error; ash lets it go (as if you'd written just &), but bash complains. Evidently your sh is some ash variant (such as dash, which is /bin/sh on many Debian derivatives).

Related questions

How can I split a shell command over multiple lines when using an IF statement?

How can I split a command over multiple lines in the shell, when the command is part of an if statement? This works: if ! fab --fabfile=.deploy/fabfile.py --forward-agent --disable-known-hosts deploy:$target; then rc=1 fi This doesn't work: # does …

Read More
Command not found error in Bash variable assignment

I have this script called test.sh: #!/bin/bash STR = "Hello World" echo $STR when I run sh test.sh I get this: test.sh: line 2: STR: command not found What am I doing wrong? I look at extremely basic/…

Read More
What is the benefit of using $() instead of backticks in shell scripts?

There are two ways to capture the output of command line in bash: Legacy Bourne shell backticks ``: var=`command` $() syntax (which as far as I know is Bash specific, or at least not supported by non-POSIX old shells like original …

Read More