Script to count lines from 'jobs' not working ...

SlowCoder · 05-01-2007, 09:58 PM

I wrote the following script ...

Code:

#!/bin/bash

if [ `jobs|wc -l` = 0 ]
        then
                echo 'There are no jobs'
        else
                echo 'There are some jobs'
fi

When I execute it, it always tells me 'There are no jobs', even if there are stopped jobs in the shell. Running "jobs|wc -l" directly at the CLI works as expected.

What's broken in my script?

druuna · 05-01-2007, 11:24 PM

Hi,

When you start a script, a new shell is started. That new shell has no jobs (waiting, running or stopped).

You could remove the #!/bin/bash line and parse the file instead of executing it (. filename instead of filename or ./filename).

Hope this helps.

jlliagre · 05-02-2007, 12:38 AM

You can also use shell functions or aliases, like that one:

Code:

$ alias j='echo there are $([[ $(jobs|wc -l) -eq 0 ]] && echo no || echo some) jobs'
$ j
there are no jobs
$ sleep 10 &
$ j
there are some jobs
$

SlowCoder · 05-02-2007, 07:53 AM

Thank you, both of you, for the options you've given. I'm looking into both.

However, can the parsing explanation be explained in more detail?

It seems to me that the current major hurdle is retrieving the value I desire from within the current shell context, not a new one.

If I remove the #!/bin/bash from my code, will that allow it to run in the current shell? I tried it with it and without, with same results.

druuna · 05-02-2007, 09:18 AM

Hi,

If you edit your file (remove the hash-bang) and make it like this:

Code:

if [ `jobs|wc -l` = 0 ]
        then
                echo 'There are no jobs'
        else
                echo 'There are some jobs'
fi

And parse it:

Code:

 $ ls -l example 
-rw-r-----  1 druuna internet 137 May  2 16:07 example

$ . example 
There are no jobs

As you can see the file doesn't even need execute permissions. Do mind the space between the dot and the filename.

The major difference between parsing and executing a file is the way the shell is used. Parsing is done in the shell you are in, while executing will start a new shell and runs the program in the new shell.

jlliagre · 05-02-2007, 09:56 AM

Quote:

Originally Posted by SlowCoder

If I remove the #!/bin/bash from my code, will that allow it to run in the current shell?

No, the prefix is unrelated, it's the way you launch the script that matters.

Quote:

I tried it with it and without, with same results.

Indeed, the #! prefix is only used when the script is executed by the O/S as an executable program to tell what command interpreter to use.
When you run it with the shell "." command, the whole first line is ignored as it starts with "#" which is the comment prefix.