run-config.sh: Removed INEP check

The regular expression validation wasn't complete nor necessary, because the
web service server checks the INEP, looking up for it in the database.
However, the empty INEP check is still done by the client binary.

Signed-off-by: Erik Alexandre Pucci <eap08@c3sl.ufpr.br>
Signed-off-by: Danilo K. S. Yorinori <danilok@c3sl.ufpr.br>

run-config.sh

@@ -48,7 +48,6 @@ cat > run.sh << 'EOF'
 dirname=$(dirname $0)
 basename=$(basename ${dirname})
 bindir=${dirname}/bin
-inepRE="^[A-Z]{2}?[[:digit:]]{8}$"
 
 # Redirects all error output to log file
 exec 2>> ${dirname}/run.log
@@ -62,16 +61,6 @@ source ${dirname}/common.sh
 url="--url=http://seed.c3sl.ufpr.br/tomcat/axis/Seed2.jws"
 inep=$(cat ${dirname}/conf/inep)
 
-# Check INEP integrity: the egrep test verifies if INEP is valid, returning
-# an empty string if it isn't. The first test checks if INEP is empty before
-# doing the second test. If it isn't empty, the regular expression occurs.
-# Otherwise, the INEP is accepted and the program continues with the
-# execution. In short, the test allows empty and valid INEPs.
-if test -n "${inep}" -a -z "$(egrep ${inepRE} <<< ${inep})"; then
-    echo "INEP format error." >> ${dirname}/run.log
-    exit 100
-fi
-
 getProxyConf
 proxy="${phost} ${pport} ${puid} ${ppasswd}"