How do I set environment variables?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
72
down vote

favorite
21












I'm trying to set up Apache Tomcat on my pc, and it wants me to set up an environment variable for CATALINA_HOME. Does any know how to do this?







share|improve this question

























    up vote
    72
    down vote

    favorite
    21












    I'm trying to set up Apache Tomcat on my pc, and it wants me to set up an environment variable for CATALINA_HOME. Does any know how to do this?







    share|improve this question























      up vote
      72
      down vote

      favorite
      21









      up vote
      72
      down vote

      favorite
      21






      21





      I'm trying to set up Apache Tomcat on my pc, and it wants me to set up an environment variable for CATALINA_HOME. Does any know how to do this?







      share|improve this question













      I'm trying to set up Apache Tomcat on my pc, and it wants me to set up an environment variable for CATALINA_HOME. Does any know how to do this?









      share|improve this question












      share|improve this question




      share|improve this question








      edited Nov 27 '10 at 10:27









      Roger Light

      1,249920




      1,249920









      asked Aug 3 '10 at 16:31









      jumpnett

      2,52172843




      2,52172843




















          6 Answers
          6






          active

          oldest

          votes

















          up vote
          72
          down vote



          accepted










          In bash you can set variables like this:



          export CATALINA_HOME=/opt/catalina


          most other shells follow this convention, but not all. You can set it permanently in ~/.profile for bash (and as before, other shells have other locations)



          • https://help.ubuntu.com/community/EnvironmentVariables

          • Where to declare environment variables?





          share|improve this answer



















          • 6




            for session-wide variables, help.ubuntu.com recommends ~/.profile as probably the best file for placing environment variable assignments in, since it gets executed automatically by the DisplayManager during the startup process desktop session as well as by the login shell when one logs-in from the textual console.
            – McDowell
            Aug 4 '10 at 21:49










          • Updated the answer. The reason why i used .bashrc instead was that at some point .profile wasn't sourced automatically. But if it works now, it's better to use it.
            – Ressu
            Aug 5 '10 at 5:07






          • 4




            Setting it in ~/.profile doesn't work for me. It works in ~/.bashrc though.
            – jumpnett
            Aug 7 '10 at 0:56











          • Setting it in ~/.bash_profile works as well.
            – jumpnett
            Jan 31 '13 at 0:45











          • There is also a system wide file in /etc. This works but is per user.
            – wheredidthatnamecomefrom
            Nov 25 '17 at 18:45

















          up vote
          23
          down vote













          Environment variables should already work



          If you are using the tomcat6 package from the Ubuntu repositories, then the CATALINA_HOME and other environment variables are already set, in the /etc/init.d/tomcat6 startup script.



          If you are installing tomcat outside the package manager (hopefully in /opt or somewhere else outside the managed file system), then running the TOMCAT/bin/startup.sh should use the relative location to define the CATALINA_HOME.



          Setting the Environment variable



          If for some reason you still need to set an environment variable you can open a terminal window and type in the command:



          export CATALINA_HOME=/path/to/the/root/folder/of/tomcat


          This environment variable will now work within that terminal window, but if you open another window or logout/login you loose that setting.



          Make the environment variable permanent



          To make the environment variable setting permanent, there are several places you can define the setting.



          To be really sure the setting is being picked up, add the above setting to one of the startup script for tomcat:



          yourtomcatfolder/bin/startup.sh

          yourtomcatfolder/bin/catalina.sh


          Note: startup.sh calls the catalina.sh. You should add the setting at the start of one of these files (after any initial comments)



          The standard way for global environment variables would be to add an entry in /etc/environment (you do not use the command export in this file as it is not a normal bash script)



          CATALINA_HOME=/path/to/the/root/folder/of/tomcat


          Not recommended



          You can set the environment variables in the bash (command line shell) configuration files, but these are not recommended as they are not always picked up (eg. if you are running a server that you dont login to to run tomcat):
          ~/.bashrc |
          ~/.profile |
          /etc.bash.bashrc |
          /etc/profile






          share|improve this answer

















          • 4




            It should not be the startup or catalina scripts, but the setenv.sh or setenv.bat script, creating it if needed: "Apart from CATALINA_HOME and CATALINA_BASE, all environment variables can be specified in the "setenv" script. The script is placed either into CATALINA_BASE/bin or into CATALINA_HOME/bin directory and is named setenv.bat (on Windows) or setenv.sh (on *nix). The file has to be readable." (Running The Apache Tomcat 7.0 Servlet/JSP Container, Section 3.4)
            – Olathe
            Oct 5 '13 at 0:53

















          up vote
          10
          down vote













          To set permanent environment variables in latest Ubuntu versions (from 14.04 and above)
          add the variables to /etc/environment. For that follow the below instructions,



          Open the terminal and run



          sudo -H gedit /etc/environment


          the provide your password, then in the prompted text file



          then add the variables like



          ANT_HOME="/opt/ANT/"


          Sample of the /etc/environment is given below



          PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
          JAVA_HOME="/usr/lib/jvm/java-8-oracle/"
          AXIS2_HOME="/opt/axis2-1.7.4/"
          ANT_HOME="/opt/apache-ant-1.9.7/"





          share|improve this answer






























            up vote
            6
            down vote













            The best place for this depends on how and where you've installed Tomcat, what applications you want to pick up this setting and how global you want the scope to be.



            The Ubuntu documentation on Environment Variables discusses the pros and cons of the various options.






            share|improve this answer





















            • What are you referring to when you say, "best place for this"?
              – jumpnett
              Aug 3 '10 at 22:58










            • @jumpnett - I mean where to make the setting persistent so that it is always available to the applications depending on it. Unless you're happy typing the setting in every time or want to write your own script.
              – McDowell
              Aug 4 '10 at 21:44

















            up vote
            2
            down vote













            nano ~/.bashrc


            This will most likely contain quite a bit of data already. Most of the definitions here are for setting bash options, which are unrelated to environmental variables. You can set environmental variables just like you would from the command line:



            export VARNAME=value


            LINK



            I tested it on Ubuntu 16.04. Works great.






            share|improve this answer




























              up vote
              1
              down vote













              After going through Ubuntu Documentation on Environment Variables, I came up with following workaround:



              ##Save & run the following in a shell script,

              export ENVIRON_VAR_NAME = Value
              # any other initializations like
              export PATH=$PWD:$PATH
              bash


              The last line creates a child shell, which inherits Environment Variable values from parent shell (which have just been set).






              share|improve this answer























                Your Answer







                StackExchange.ready(function()
                var channelOptions =
                tags: "".split(" "),
                id: "89"
                ;
                initTagRenderer("".split(" "), "".split(" "), channelOptions);

                StackExchange.using("externalEditor", function()
                // Have to fire editor after snippets, if snippets enabled
                if (StackExchange.settings.snippets.snippetsEnabled)
                StackExchange.using("snippets", function()
                createEditor();
                );

                else
                createEditor();

                );

                function createEditor()
                StackExchange.prepareEditor(
                heartbeatType: 'answer',
                convertImagesToLinks: true,
                noModals: false,
                showLowRepImageUploadWarning: true,
                reputationToPostImages: 10,
                bindNavPrevention: true,
                postfix: "",
                onDemand: true,
                discardSelector: ".discard-answer"
                ,immediatelyShowMarkdownHelp:true
                );



                );








                 

                draft saved


                draft discarded


















                StackExchange.ready(
                function ()
                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f730%2fhow-do-i-set-environment-variables%23new-answer', 'question_page');

                );

                Post as a guest






























                6 Answers
                6






                active

                oldest

                votes








                6 Answers
                6






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes








                up vote
                72
                down vote



                accepted










                In bash you can set variables like this:



                export CATALINA_HOME=/opt/catalina


                most other shells follow this convention, but not all. You can set it permanently in ~/.profile for bash (and as before, other shells have other locations)



                • https://help.ubuntu.com/community/EnvironmentVariables

                • Where to declare environment variables?





                share|improve this answer



















                • 6




                  for session-wide variables, help.ubuntu.com recommends ~/.profile as probably the best file for placing environment variable assignments in, since it gets executed automatically by the DisplayManager during the startup process desktop session as well as by the login shell when one logs-in from the textual console.
                  – McDowell
                  Aug 4 '10 at 21:49










                • Updated the answer. The reason why i used .bashrc instead was that at some point .profile wasn't sourced automatically. But if it works now, it's better to use it.
                  – Ressu
                  Aug 5 '10 at 5:07






                • 4




                  Setting it in ~/.profile doesn't work for me. It works in ~/.bashrc though.
                  – jumpnett
                  Aug 7 '10 at 0:56











                • Setting it in ~/.bash_profile works as well.
                  – jumpnett
                  Jan 31 '13 at 0:45











                • There is also a system wide file in /etc. This works but is per user.
                  – wheredidthatnamecomefrom
                  Nov 25 '17 at 18:45














                up vote
                72
                down vote



                accepted










                In bash you can set variables like this:



                export CATALINA_HOME=/opt/catalina


                most other shells follow this convention, but not all. You can set it permanently in ~/.profile for bash (and as before, other shells have other locations)



                • https://help.ubuntu.com/community/EnvironmentVariables

                • Where to declare environment variables?





                share|improve this answer



















                • 6




                  for session-wide variables, help.ubuntu.com recommends ~/.profile as probably the best file for placing environment variable assignments in, since it gets executed automatically by the DisplayManager during the startup process desktop session as well as by the login shell when one logs-in from the textual console.
                  – McDowell
                  Aug 4 '10 at 21:49










                • Updated the answer. The reason why i used .bashrc instead was that at some point .profile wasn't sourced automatically. But if it works now, it's better to use it.
                  – Ressu
                  Aug 5 '10 at 5:07






                • 4




                  Setting it in ~/.profile doesn't work for me. It works in ~/.bashrc though.
                  – jumpnett
                  Aug 7 '10 at 0:56











                • Setting it in ~/.bash_profile works as well.
                  – jumpnett
                  Jan 31 '13 at 0:45











                • There is also a system wide file in /etc. This works but is per user.
                  – wheredidthatnamecomefrom
                  Nov 25 '17 at 18:45












                up vote
                72
                down vote



                accepted







                up vote
                72
                down vote



                accepted






                In bash you can set variables like this:



                export CATALINA_HOME=/opt/catalina


                most other shells follow this convention, but not all. You can set it permanently in ~/.profile for bash (and as before, other shells have other locations)



                • https://help.ubuntu.com/community/EnvironmentVariables

                • Where to declare environment variables?





                share|improve this answer















                In bash you can set variables like this:



                export CATALINA_HOME=/opt/catalina


                most other shells follow this convention, but not all. You can set it permanently in ~/.profile for bash (and as before, other shells have other locations)



                • https://help.ubuntu.com/community/EnvironmentVariables

                • Where to declare environment variables?






                share|improve this answer















                share|improve this answer



                share|improve this answer








                edited Apr 13 '17 at 12:23









                Community♦

                1




                1











                answered Aug 3 '10 at 16:34









                Ressu

                7,94012927




                7,94012927







                • 6




                  for session-wide variables, help.ubuntu.com recommends ~/.profile as probably the best file for placing environment variable assignments in, since it gets executed automatically by the DisplayManager during the startup process desktop session as well as by the login shell when one logs-in from the textual console.
                  – McDowell
                  Aug 4 '10 at 21:49










                • Updated the answer. The reason why i used .bashrc instead was that at some point .profile wasn't sourced automatically. But if it works now, it's better to use it.
                  – Ressu
                  Aug 5 '10 at 5:07






                • 4




                  Setting it in ~/.profile doesn't work for me. It works in ~/.bashrc though.
                  – jumpnett
                  Aug 7 '10 at 0:56











                • Setting it in ~/.bash_profile works as well.
                  – jumpnett
                  Jan 31 '13 at 0:45











                • There is also a system wide file in /etc. This works but is per user.
                  – wheredidthatnamecomefrom
                  Nov 25 '17 at 18:45












                • 6




                  for session-wide variables, help.ubuntu.com recommends ~/.profile as probably the best file for placing environment variable assignments in, since it gets executed automatically by the DisplayManager during the startup process desktop session as well as by the login shell when one logs-in from the textual console.
                  – McDowell
                  Aug 4 '10 at 21:49










                • Updated the answer. The reason why i used .bashrc instead was that at some point .profile wasn't sourced automatically. But if it works now, it's better to use it.
                  – Ressu
                  Aug 5 '10 at 5:07






                • 4




                  Setting it in ~/.profile doesn't work for me. It works in ~/.bashrc though.
                  – jumpnett
                  Aug 7 '10 at 0:56











                • Setting it in ~/.bash_profile works as well.
                  – jumpnett
                  Jan 31 '13 at 0:45











                • There is also a system wide file in /etc. This works but is per user.
                  – wheredidthatnamecomefrom
                  Nov 25 '17 at 18:45







                6




                6




                for session-wide variables, help.ubuntu.com recommends ~/.profile as probably the best file for placing environment variable assignments in, since it gets executed automatically by the DisplayManager during the startup process desktop session as well as by the login shell when one logs-in from the textual console.
                – McDowell
                Aug 4 '10 at 21:49




                for session-wide variables, help.ubuntu.com recommends ~/.profile as probably the best file for placing environment variable assignments in, since it gets executed automatically by the DisplayManager during the startup process desktop session as well as by the login shell when one logs-in from the textual console.
                – McDowell
                Aug 4 '10 at 21:49












                Updated the answer. The reason why i used .bashrc instead was that at some point .profile wasn't sourced automatically. But if it works now, it's better to use it.
                – Ressu
                Aug 5 '10 at 5:07




                Updated the answer. The reason why i used .bashrc instead was that at some point .profile wasn't sourced automatically. But if it works now, it's better to use it.
                – Ressu
                Aug 5 '10 at 5:07




                4




                4




                Setting it in ~/.profile doesn't work for me. It works in ~/.bashrc though.
                – jumpnett
                Aug 7 '10 at 0:56





                Setting it in ~/.profile doesn't work for me. It works in ~/.bashrc though.
                – jumpnett
                Aug 7 '10 at 0:56













                Setting it in ~/.bash_profile works as well.
                – jumpnett
                Jan 31 '13 at 0:45





                Setting it in ~/.bash_profile works as well.
                – jumpnett
                Jan 31 '13 at 0:45













                There is also a system wide file in /etc. This works but is per user.
                – wheredidthatnamecomefrom
                Nov 25 '17 at 18:45




                There is also a system wide file in /etc. This works but is per user.
                – wheredidthatnamecomefrom
                Nov 25 '17 at 18:45












                up vote
                23
                down vote













                Environment variables should already work



                If you are using the tomcat6 package from the Ubuntu repositories, then the CATALINA_HOME and other environment variables are already set, in the /etc/init.d/tomcat6 startup script.



                If you are installing tomcat outside the package manager (hopefully in /opt or somewhere else outside the managed file system), then running the TOMCAT/bin/startup.sh should use the relative location to define the CATALINA_HOME.



                Setting the Environment variable



                If for some reason you still need to set an environment variable you can open a terminal window and type in the command:



                export CATALINA_HOME=/path/to/the/root/folder/of/tomcat


                This environment variable will now work within that terminal window, but if you open another window or logout/login you loose that setting.



                Make the environment variable permanent



                To make the environment variable setting permanent, there are several places you can define the setting.



                To be really sure the setting is being picked up, add the above setting to one of the startup script for tomcat:



                yourtomcatfolder/bin/startup.sh

                yourtomcatfolder/bin/catalina.sh


                Note: startup.sh calls the catalina.sh. You should add the setting at the start of one of these files (after any initial comments)



                The standard way for global environment variables would be to add an entry in /etc/environment (you do not use the command export in this file as it is not a normal bash script)



                CATALINA_HOME=/path/to/the/root/folder/of/tomcat


                Not recommended



                You can set the environment variables in the bash (command line shell) configuration files, but these are not recommended as they are not always picked up (eg. if you are running a server that you dont login to to run tomcat):
                ~/.bashrc |
                ~/.profile |
                /etc.bash.bashrc |
                /etc/profile






                share|improve this answer

















                • 4




                  It should not be the startup or catalina scripts, but the setenv.sh or setenv.bat script, creating it if needed: "Apart from CATALINA_HOME and CATALINA_BASE, all environment variables can be specified in the "setenv" script. The script is placed either into CATALINA_BASE/bin or into CATALINA_HOME/bin directory and is named setenv.bat (on Windows) or setenv.sh (on *nix). The file has to be readable." (Running The Apache Tomcat 7.0 Servlet/JSP Container, Section 3.4)
                  – Olathe
                  Oct 5 '13 at 0:53














                up vote
                23
                down vote













                Environment variables should already work



                If you are using the tomcat6 package from the Ubuntu repositories, then the CATALINA_HOME and other environment variables are already set, in the /etc/init.d/tomcat6 startup script.



                If you are installing tomcat outside the package manager (hopefully in /opt or somewhere else outside the managed file system), then running the TOMCAT/bin/startup.sh should use the relative location to define the CATALINA_HOME.



                Setting the Environment variable



                If for some reason you still need to set an environment variable you can open a terminal window and type in the command:



                export CATALINA_HOME=/path/to/the/root/folder/of/tomcat


                This environment variable will now work within that terminal window, but if you open another window or logout/login you loose that setting.



                Make the environment variable permanent



                To make the environment variable setting permanent, there are several places you can define the setting.



                To be really sure the setting is being picked up, add the above setting to one of the startup script for tomcat:



                yourtomcatfolder/bin/startup.sh

                yourtomcatfolder/bin/catalina.sh


                Note: startup.sh calls the catalina.sh. You should add the setting at the start of one of these files (after any initial comments)



                The standard way for global environment variables would be to add an entry in /etc/environment (you do not use the command export in this file as it is not a normal bash script)



                CATALINA_HOME=/path/to/the/root/folder/of/tomcat


                Not recommended



                You can set the environment variables in the bash (command line shell) configuration files, but these are not recommended as they are not always picked up (eg. if you are running a server that you dont login to to run tomcat):
                ~/.bashrc |
                ~/.profile |
                /etc.bash.bashrc |
                /etc/profile






                share|improve this answer

















                • 4




                  It should not be the startup or catalina scripts, but the setenv.sh or setenv.bat script, creating it if needed: "Apart from CATALINA_HOME and CATALINA_BASE, all environment variables can be specified in the "setenv" script. The script is placed either into CATALINA_BASE/bin or into CATALINA_HOME/bin directory and is named setenv.bat (on Windows) or setenv.sh (on *nix). The file has to be readable." (Running The Apache Tomcat 7.0 Servlet/JSP Container, Section 3.4)
                  – Olathe
                  Oct 5 '13 at 0:53












                up vote
                23
                down vote










                up vote
                23
                down vote









                Environment variables should already work



                If you are using the tomcat6 package from the Ubuntu repositories, then the CATALINA_HOME and other environment variables are already set, in the /etc/init.d/tomcat6 startup script.



                If you are installing tomcat outside the package manager (hopefully in /opt or somewhere else outside the managed file system), then running the TOMCAT/bin/startup.sh should use the relative location to define the CATALINA_HOME.



                Setting the Environment variable



                If for some reason you still need to set an environment variable you can open a terminal window and type in the command:



                export CATALINA_HOME=/path/to/the/root/folder/of/tomcat


                This environment variable will now work within that terminal window, but if you open another window or logout/login you loose that setting.



                Make the environment variable permanent



                To make the environment variable setting permanent, there are several places you can define the setting.



                To be really sure the setting is being picked up, add the above setting to one of the startup script for tomcat:



                yourtomcatfolder/bin/startup.sh

                yourtomcatfolder/bin/catalina.sh


                Note: startup.sh calls the catalina.sh. You should add the setting at the start of one of these files (after any initial comments)



                The standard way for global environment variables would be to add an entry in /etc/environment (you do not use the command export in this file as it is not a normal bash script)



                CATALINA_HOME=/path/to/the/root/folder/of/tomcat


                Not recommended



                You can set the environment variables in the bash (command line shell) configuration files, but these are not recommended as they are not always picked up (eg. if you are running a server that you dont login to to run tomcat):
                ~/.bashrc |
                ~/.profile |
                /etc.bash.bashrc |
                /etc/profile






                share|improve this answer













                Environment variables should already work



                If you are using the tomcat6 package from the Ubuntu repositories, then the CATALINA_HOME and other environment variables are already set, in the /etc/init.d/tomcat6 startup script.



                If you are installing tomcat outside the package manager (hopefully in /opt or somewhere else outside the managed file system), then running the TOMCAT/bin/startup.sh should use the relative location to define the CATALINA_HOME.



                Setting the Environment variable



                If for some reason you still need to set an environment variable you can open a terminal window and type in the command:



                export CATALINA_HOME=/path/to/the/root/folder/of/tomcat


                This environment variable will now work within that terminal window, but if you open another window or logout/login you loose that setting.



                Make the environment variable permanent



                To make the environment variable setting permanent, there are several places you can define the setting.



                To be really sure the setting is being picked up, add the above setting to one of the startup script for tomcat:



                yourtomcatfolder/bin/startup.sh

                yourtomcatfolder/bin/catalina.sh


                Note: startup.sh calls the catalina.sh. You should add the setting at the start of one of these files (after any initial comments)



                The standard way for global environment variables would be to add an entry in /etc/environment (you do not use the command export in this file as it is not a normal bash script)



                CATALINA_HOME=/path/to/the/root/folder/of/tomcat


                Not recommended



                You can set the environment variables in the bash (command line shell) configuration files, but these are not recommended as they are not always picked up (eg. if you are running a server that you dont login to to run tomcat):
                ~/.bashrc |
                ~/.profile |
                /etc.bash.bashrc |
                /etc/profile







                share|improve this answer













                share|improve this answer



                share|improve this answer











                answered Aug 5 '10 at 7:03









                jr0cket

                2,67311413




                2,67311413







                • 4




                  It should not be the startup or catalina scripts, but the setenv.sh or setenv.bat script, creating it if needed: "Apart from CATALINA_HOME and CATALINA_BASE, all environment variables can be specified in the "setenv" script. The script is placed either into CATALINA_BASE/bin or into CATALINA_HOME/bin directory and is named setenv.bat (on Windows) or setenv.sh (on *nix). The file has to be readable." (Running The Apache Tomcat 7.0 Servlet/JSP Container, Section 3.4)
                  – Olathe
                  Oct 5 '13 at 0:53












                • 4




                  It should not be the startup or catalina scripts, but the setenv.sh or setenv.bat script, creating it if needed: "Apart from CATALINA_HOME and CATALINA_BASE, all environment variables can be specified in the "setenv" script. The script is placed either into CATALINA_BASE/bin or into CATALINA_HOME/bin directory and is named setenv.bat (on Windows) or setenv.sh (on *nix). The file has to be readable." (Running The Apache Tomcat 7.0 Servlet/JSP Container, Section 3.4)
                  – Olathe
                  Oct 5 '13 at 0:53







                4




                4




                It should not be the startup or catalina scripts, but the setenv.sh or setenv.bat script, creating it if needed: "Apart from CATALINA_HOME and CATALINA_BASE, all environment variables can be specified in the "setenv" script. The script is placed either into CATALINA_BASE/bin or into CATALINA_HOME/bin directory and is named setenv.bat (on Windows) or setenv.sh (on *nix). The file has to be readable." (Running The Apache Tomcat 7.0 Servlet/JSP Container, Section 3.4)
                – Olathe
                Oct 5 '13 at 0:53




                It should not be the startup or catalina scripts, but the setenv.sh or setenv.bat script, creating it if needed: "Apart from CATALINA_HOME and CATALINA_BASE, all environment variables can be specified in the "setenv" script. The script is placed either into CATALINA_BASE/bin or into CATALINA_HOME/bin directory and is named setenv.bat (on Windows) or setenv.sh (on *nix). The file has to be readable." (Running The Apache Tomcat 7.0 Servlet/JSP Container, Section 3.4)
                – Olathe
                Oct 5 '13 at 0:53










                up vote
                10
                down vote













                To set permanent environment variables in latest Ubuntu versions (from 14.04 and above)
                add the variables to /etc/environment. For that follow the below instructions,



                Open the terminal and run



                sudo -H gedit /etc/environment


                the provide your password, then in the prompted text file



                then add the variables like



                ANT_HOME="/opt/ANT/"


                Sample of the /etc/environment is given below



                PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
                JAVA_HOME="/usr/lib/jvm/java-8-oracle/"
                AXIS2_HOME="/opt/axis2-1.7.4/"
                ANT_HOME="/opt/apache-ant-1.9.7/"





                share|improve this answer



























                  up vote
                  10
                  down vote













                  To set permanent environment variables in latest Ubuntu versions (from 14.04 and above)
                  add the variables to /etc/environment. For that follow the below instructions,



                  Open the terminal and run



                  sudo -H gedit /etc/environment


                  the provide your password, then in the prompted text file



                  then add the variables like



                  ANT_HOME="/opt/ANT/"


                  Sample of the /etc/environment is given below



                  PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
                  JAVA_HOME="/usr/lib/jvm/java-8-oracle/"
                  AXIS2_HOME="/opt/axis2-1.7.4/"
                  ANT_HOME="/opt/apache-ant-1.9.7/"





                  share|improve this answer

























                    up vote
                    10
                    down vote










                    up vote
                    10
                    down vote









                    To set permanent environment variables in latest Ubuntu versions (from 14.04 and above)
                    add the variables to /etc/environment. For that follow the below instructions,



                    Open the terminal and run



                    sudo -H gedit /etc/environment


                    the provide your password, then in the prompted text file



                    then add the variables like



                    ANT_HOME="/opt/ANT/"


                    Sample of the /etc/environment is given below



                    PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
                    JAVA_HOME="/usr/lib/jvm/java-8-oracle/"
                    AXIS2_HOME="/opt/axis2-1.7.4/"
                    ANT_HOME="/opt/apache-ant-1.9.7/"





                    share|improve this answer















                    To set permanent environment variables in latest Ubuntu versions (from 14.04 and above)
                    add the variables to /etc/environment. For that follow the below instructions,



                    Open the terminal and run



                    sudo -H gedit /etc/environment


                    the provide your password, then in the prompted text file



                    then add the variables like



                    ANT_HOME="/opt/ANT/"


                    Sample of the /etc/environment is given below



                    PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
                    JAVA_HOME="/usr/lib/jvm/java-8-oracle/"
                    AXIS2_HOME="/opt/axis2-1.7.4/"
                    ANT_HOME="/opt/apache-ant-1.9.7/"






                    share|improve this answer















                    share|improve this answer



                    share|improve this answer








                    edited Nov 16 '16 at 5:18









                    muru

                    128k19269459




                    128k19269459











                    answered Nov 16 '16 at 5:11









                    Kasun Siyambalapitiya

                    283515




                    283515




















                        up vote
                        6
                        down vote













                        The best place for this depends on how and where you've installed Tomcat, what applications you want to pick up this setting and how global you want the scope to be.



                        The Ubuntu documentation on Environment Variables discusses the pros and cons of the various options.






                        share|improve this answer





















                        • What are you referring to when you say, "best place for this"?
                          – jumpnett
                          Aug 3 '10 at 22:58










                        • @jumpnett - I mean where to make the setting persistent so that it is always available to the applications depending on it. Unless you're happy typing the setting in every time or want to write your own script.
                          – McDowell
                          Aug 4 '10 at 21:44














                        up vote
                        6
                        down vote













                        The best place for this depends on how and where you've installed Tomcat, what applications you want to pick up this setting and how global you want the scope to be.



                        The Ubuntu documentation on Environment Variables discusses the pros and cons of the various options.






                        share|improve this answer





















                        • What are you referring to when you say, "best place for this"?
                          – jumpnett
                          Aug 3 '10 at 22:58










                        • @jumpnett - I mean where to make the setting persistent so that it is always available to the applications depending on it. Unless you're happy typing the setting in every time or want to write your own script.
                          – McDowell
                          Aug 4 '10 at 21:44












                        up vote
                        6
                        down vote










                        up vote
                        6
                        down vote









                        The best place for this depends on how and where you've installed Tomcat, what applications you want to pick up this setting and how global you want the scope to be.



                        The Ubuntu documentation on Environment Variables discusses the pros and cons of the various options.






                        share|improve this answer













                        The best place for this depends on how and where you've installed Tomcat, what applications you want to pick up this setting and how global you want the scope to be.



                        The Ubuntu documentation on Environment Variables discusses the pros and cons of the various options.







                        share|improve this answer













                        share|improve this answer



                        share|improve this answer











                        answered Aug 3 '10 at 22:17









                        McDowell

                        253612




                        253612











                        • What are you referring to when you say, "best place for this"?
                          – jumpnett
                          Aug 3 '10 at 22:58










                        • @jumpnett - I mean where to make the setting persistent so that it is always available to the applications depending on it. Unless you're happy typing the setting in every time or want to write your own script.
                          – McDowell
                          Aug 4 '10 at 21:44
















                        • What are you referring to when you say, "best place for this"?
                          – jumpnett
                          Aug 3 '10 at 22:58










                        • @jumpnett - I mean where to make the setting persistent so that it is always available to the applications depending on it. Unless you're happy typing the setting in every time or want to write your own script.
                          – McDowell
                          Aug 4 '10 at 21:44















                        What are you referring to when you say, "best place for this"?
                        – jumpnett
                        Aug 3 '10 at 22:58




                        What are you referring to when you say, "best place for this"?
                        – jumpnett
                        Aug 3 '10 at 22:58












                        @jumpnett - I mean where to make the setting persistent so that it is always available to the applications depending on it. Unless you're happy typing the setting in every time or want to write your own script.
                        – McDowell
                        Aug 4 '10 at 21:44




                        @jumpnett - I mean where to make the setting persistent so that it is always available to the applications depending on it. Unless you're happy typing the setting in every time or want to write your own script.
                        – McDowell
                        Aug 4 '10 at 21:44










                        up vote
                        2
                        down vote













                        nano ~/.bashrc


                        This will most likely contain quite a bit of data already. Most of the definitions here are for setting bash options, which are unrelated to environmental variables. You can set environmental variables just like you would from the command line:



                        export VARNAME=value


                        LINK



                        I tested it on Ubuntu 16.04. Works great.






                        share|improve this answer

























                          up vote
                          2
                          down vote













                          nano ~/.bashrc


                          This will most likely contain quite a bit of data already. Most of the definitions here are for setting bash options, which are unrelated to environmental variables. You can set environmental variables just like you would from the command line:



                          export VARNAME=value


                          LINK



                          I tested it on Ubuntu 16.04. Works great.






                          share|improve this answer























                            up vote
                            2
                            down vote










                            up vote
                            2
                            down vote









                            nano ~/.bashrc


                            This will most likely contain quite a bit of data already. Most of the definitions here are for setting bash options, which are unrelated to environmental variables. You can set environmental variables just like you would from the command line:



                            export VARNAME=value


                            LINK



                            I tested it on Ubuntu 16.04. Works great.






                            share|improve this answer













                            nano ~/.bashrc


                            This will most likely contain quite a bit of data already. Most of the definitions here are for setting bash options, which are unrelated to environmental variables. You can set environmental variables just like you would from the command line:



                            export VARNAME=value


                            LINK



                            I tested it on Ubuntu 16.04. Works great.







                            share|improve this answer













                            share|improve this answer



                            share|improve this answer











                            answered Jan 3 at 11:00









                            Sunny127

                            17113




                            17113




















                                up vote
                                1
                                down vote













                                After going through Ubuntu Documentation on Environment Variables, I came up with following workaround:



                                ##Save & run the following in a shell script,

                                export ENVIRON_VAR_NAME = Value
                                # any other initializations like
                                export PATH=$PWD:$PATH
                                bash


                                The last line creates a child shell, which inherits Environment Variable values from parent shell (which have just been set).






                                share|improve this answer



























                                  up vote
                                  1
                                  down vote













                                  After going through Ubuntu Documentation on Environment Variables, I came up with following workaround:



                                  ##Save & run the following in a shell script,

                                  export ENVIRON_VAR_NAME = Value
                                  # any other initializations like
                                  export PATH=$PWD:$PATH
                                  bash


                                  The last line creates a child shell, which inherits Environment Variable values from parent shell (which have just been set).






                                  share|improve this answer

























                                    up vote
                                    1
                                    down vote










                                    up vote
                                    1
                                    down vote









                                    After going through Ubuntu Documentation on Environment Variables, I came up with following workaround:



                                    ##Save & run the following in a shell script,

                                    export ENVIRON_VAR_NAME = Value
                                    # any other initializations like
                                    export PATH=$PWD:$PATH
                                    bash


                                    The last line creates a child shell, which inherits Environment Variable values from parent shell (which have just been set).






                                    share|improve this answer















                                    After going through Ubuntu Documentation on Environment Variables, I came up with following workaround:



                                    ##Save & run the following in a shell script,

                                    export ENVIRON_VAR_NAME = Value
                                    # any other initializations like
                                    export PATH=$PWD:$PATH
                                    bash


                                    The last line creates a child shell, which inherits Environment Variable values from parent shell (which have just been set).







                                    share|improve this answer















                                    share|improve this answer



                                    share|improve this answer








                                    edited Nov 16 '16 at 5:19









                                    muru

                                    128k19269459




                                    128k19269459











                                    answered Feb 19 '14 at 1:53









                                    Ashish Sadhwani

                                    111




                                    111






















                                         

                                        draft saved


                                        draft discarded


























                                         


                                        draft saved


                                        draft discarded














                                        StackExchange.ready(
                                        function ()
                                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f730%2fhow-do-i-set-environment-variables%23new-answer', 'question_page');

                                        );

                                        Post as a guest













































































                                        Popular posts from this blog

                                        pylint3 and pip3 broken

                                        Missing snmpget and snmpwalk

                                        How to enroll fingerprints to Ubuntu 17.10 with VFS491