Skip to main content

How to check if environment variable is set using shell script?

If you are wondering how can we check whether an environment variable is set or not in the system, here are few methods :

1. Manually
a. Run “set” command on the shell prompt, it will list out all the variables set in the system :
# set
b. Run “echo” command on the shell to print the value of the environment variable :
# echo $<environment variable>

2. Through Shell Script
Let say we intent to check whether environment variable “envVar” is set or not?

a. Method 1 – checking if “envVar” is set to “” (no value) :
if [ "$envVar" == "" ]
then
echo “envVar is not set”
else
echo “envVar is set”
fi

b.Method 2 – checking if “envVar” is non NULL :
if [ -n "$envVar" ]
then
echo “envVar has non NULL value, it is set.”
else
echo “envVar has NULL value, it is not set.”
fi

Comments

Popular posts from this blog

JUnit – Run unit test in an Sequence / Order

In JUnit, we can use @FixMethodOrder(MethodSorters.xxx) to run the test methods in a sequence or order.

import org.junit.FixMethodOrder;import org.junit.Test;import org.junit.runners.MethodSorters;importstatic org.hamcrest.CoreMatchers.is;importstatic org.junit.Assert.assertThat;//Sorts by method name@FixMethodOrder(MethodSorters.NAME_ASCENDING)publicclassExecutionOrderTest{@TestpublicvoidtestB(){assertThat(1+1,is(2));}@Testpublicvoidtest1(){assertThat(1+1,is(2));}@TestpublicvoidtestA

Create Runnable Jar - Eclipse Options

When exporting to a Runnable Jar, there are three options in eclipse Helios. Extract required libraries into JARPackage required libraries into JARCopy required libraries into sub folder next to JAR. What are differences : Extract required libraries into JAR - Extracts the actual .class files from the libraries your app uses and puts those .class files inside the runnable JAR. So, the runnable JAR will not only contain the .class files of your application, but also the .class files of all the libraries your application uses. Package required libraries into JAR - Puts the actual JAR files of the libraries into your runnable JAR. Normally, a JAR file within a JAR file cannot be loaded by the JVM. But Eclipse adds special classes to the runnable JAR to make this possible. Copy required libraries into sub folder next to JAR - Keeps the library JARs completely separate from the runnable JAR, so the runnable JAR will only contain the .class files of your application. Option #2 is convenient be…