[Openca-ocspd] How does sbin/test.sh do, and how does it work?

[o h. <oh...@ya...>]

Hi,
There is a small script named "test.sh" in the ocspd sbin directory, and when it is run, I get:

OCSP Test Script
(c) 2006 by Massimiliano Pala and OpenCA Team

Test 78 requests (serial 123):
[111111111111111111111111111111111111111111111111111111111111111111111111111111
real    0m0.250s
user    0m0.161s
sys     0m0.045s
]

I had assumed that that script was running a test against the actual ocspd, but then I noticed that even when I run it while the ocspd is not running, I get exactly the same output.
So I was looking at the script:
#!/bin/bash

echo
echo "OCSP Test Script"
echo "(c) 2006 by Massimiliano Pala and OpenCA Team"
echo

# if [ $# -lt 3 ] ; then
#       echo "Usage: $0 <CAfile> <Issuer_Cert> <URL>"
#       echo
#       echo "   example:  $0 ca-bundle.pem cacert.pem http://localhost:2560/"
#       echo
#       exit 0
# fi

cabundle=data/europki_root_ca_cert.pem
cacert=data/europki_root_ca_cert.pem
url=http://localhost:2560/

if [ "0$1" -gt 0 ] ; then
        nreq=$1;
else
        nreq=78;
fi

for ser in 123 ; do
        echo "Test $nreq requests (serial $ser):"
        echo -n "["
        time {
                for((i=0;i<$nreq;i++)); do
                        openssl ocsp -CAfile $cabundle \
                                -url $url \
                                -issuer $cacert \
                                -serial $ser 2>/dev/null >/dev/null
                                # -cert test/ocspd_cert.pem 2>/dev/null >/dev/null
                        if [ $? = 0 ] ; then
                                echo -n .
                        else
                                echo -n $?
                        fi
                done
        }
        echo  "]"
        echo
done

exit

And from that, it looks like it is running this command:
openssl ocsp -CAfile data/europki_root_ca_cert.pem -issuer data/europki_root_ca_cert.pem -url http://localhost:2560/ -serial 123
but there is no "data/europki_root_ca_cert.pem" file and also nothing is listening on port 2560, so with all of the above, I am not sure what the test.sh is actually doing and how does it even work?
Thanks,Jim