Ubuntu – Why I can’t use the CATALINA_HOME environment variable

bashcommand lineenvironment-variablesservertomcat

I am not yet a Linux guy and I have the following problem with environment variable.

So I want to add a permanent environment variable and I do in this way:

I open the /etc/profile file and I add this line at the end of this file:

CATALINA_HOME=/opt/apache-tomcat-8.0.24

Where /opt/apache-tomcat-8.0.24 is the folder that contain the tomcat installation (it contains the bin TomCat subfolder)

Then I save this file.

So I close the shell and I reopen it and I try to do:

andrea@andrea-virtual-machine:/$ sudo ./startup.sh
sudo: ./startup.sh: command not found

To start the server instead enter into /opt/apache-tomcat-8.0.24/bin/ and perform the command.

But as you can see I obtain an error. What am I missing?

Best Answer

sudo ./startup.sh command will execute the startup.sh script in your current directory.

This you should do:

Add this line to /etc/profile for setting path while booting( Permanent change)

export CATALINA_HOME=/opt/apache-tomcat-8.0.24

To set path temporarily execute above command in the current shell.

and excute this:

sudo $CATALINA_HOME/bin/startup.sh

Related Solutions

Ubuntu – the $BASH_COMMAND variable good for

Answering to the third question: of course it can be used meaningfully in the way at Bash manual clearly hints – in a trap, e. g.:

$ trap 'echo ‘$BASH_COMMAND’ failed with error code $?' ERR
$ fgfdjsa
fgfdjsa: command not found
‘fgfdjsa’ failed with error code 127
$ cat /etc/fgfdjsa
cat: /etc/fgfdjsa: No such file or directory
‘cat /etc/fgfdjsa’ failed with error code 1

Ubuntu – Set environment variable UBUNTU 18.04 (bionic) – Crontab

cron runs jobs in its own minimal environment and doesn't itself read any of the shell startup files such as those in /etc/profile.d/ - by default it's just something like

LANGUAGE=en_CA:en
HOME=/home/steeldriver
LOGNAME=steeldriver
PATH=/usr/bin:/bin
LANG=en_CA.UTF-8
SHELL=/bin/sh
PWD=/home/steeldriver

You have a couple of options:

set the variables in a script, and run that from cron. In the case of shell scripts, that's easy (just export them at the top of the script - or source an environment file if you prefer). For Python scripts you may find it easiest to wrap the python call inside a shell script where you can set up the environment first.
define the environment as a sequence of name = value pairs inside the crontab like
```
ORACLE_HOME = /usr/lib/oracle/12.2/client64
* 5 * * * /path/to/some/executable
```
(spaces are allowed around the = since it's not a script); however note that this method does not expand variables so you can't do stuff like PATH=$PATH:/whatever

See man 5 crontab for details.

Best Answer

Related Solutions

Ubuntu – the $BASH_COMMAND variable good for

Ubuntu – Set environment variable UBUNTU 18.04 (bionic) – Crontab

Related Question