Linux export for all

How to export variables that are set, all at once?

set command displays all the local variables like below. How do I export these variables all at once?

>set a=123 b="asd asd" c="hello world" 

what do you mean export all at once? you can use semi colons to define in one line. like a=123;b=»asd asd»;c=»hello world»

Your question is unclear. Is that an excerpt of set output you’re showing? If so, then it’s not bash ‘s. Do you want to export all the currently set variable including the special shell variables? Or only those 3 variables like in export a b c ?

export $ would export any defined parameter whose name starts with T . Unfortunately, there doesn’t seem to be a way to easily generate a list of all defined parameters.

5 Answers 5

Run the following command, before setting the variables:

set -a set -o allexport # self-documenting version 

To turn this option off, run set +a or set +o allexport afterwards.

set -a # or: set -o allexport . ./environment set +a 

Where environment contains:

FOO=BAR BAS='quote when using spaces, (, >, $, ; etc' 

This must be enabled before assigning to variables, though. It doesn’t do anything to previously assigned variables.

Same preliminary requirement as chosen answer . either explicitly export each variable as per

or prior to any variable assignment issue

set -a # for details see answer by @nitin 

then this works if your shell is bash ( possibly other shells as well )

your new file will contain a dump of all currently defined variables . with entries like

declare -x PORT="9000" declare -x PORT_ADMIN="3001" declare -x PORT_DOCKER_REGISTRY="5000" declare -x PORT_ENDUSER="3000" declare -x PRE_BUILD_DIR="/cryptdata6/var/log/tmp/khufu01/loud_deploy/curr/loud-build/hygge" declare -x PROJECT_ID="hygge" declare -x PROJECT_ID_BUSHIDO="bushido" 

then to jack up current shell with all those env vars issue

Источник

How to Export Variables in .Bashrc

In Linux, users can define the local variables in Bash by default. In this case, a user must export the variables for the child processes. That’s why Linux supports the export commands that update the current session per the exported variable’s updates.

Nevertheless, many users do not understand how to use the export command to the .bashrc file. In this tutorial, we will explain a complete method to export the variables in .bashrc and use them in scripts.

How to Export Variables in .Bashrc

Let’s start with the simple example of exporting a variable from a shell to the .bashrc file. First, we create a .bashrc file through the following command:

Now, create a variable and then export it in all shells. For example, set the value of the variable named example:

After that, export this variable through the following command:

You can now enter the new shell. Then, check the exported variable through the following commands:

Now, enter the following details in the file.bashrc:

Once you are done, save the file and execute it in the terminal:

The file.bashrc script exports the value from the example variable, as shown in the previous image.

Export Variables in .Bashrc and Use Them in Scripts

First, set the value of the test as the variable. Then, export it in all sessions:

Now, execute the script in the terminal to print the variable:

If you want to use this exported variable in other scripts, create a script first and then enter the following details:

Finally, run the script. The system will print the exported variable in the terminal:

The export command is not limited to the scripts related tasks. It also includes various options. For instance, you can use the -p flag to display the list of variables:

Conclusion

This is how you can easily export the variables in .bashrc and use them in the scripts. The export command is easy to use and can help you to export the variable value from the current session to all. Exporting the variables is important because the variable value is only available for the current session. You can use these exported values in different scripts.

About the author

Prateek Jangid

A passionate Linux user for personal and professional reasons, always exploring what is new in the world of Linux and sharing with my readers.

Источник

How to Set Environment Variables in Linux

In this tutorial, you will learn how to set environment variables in Ubuntu, CentOS, Red Hat, basically any Linux distribution for a single user and globally for all users. You will also learn how to list all environment variables and how to unset (clear) existing environment variables.

Environment variables are commonly used within the Bash shell. It is also a common means of configuring services and handling web application secrets.

It is not uncommon for environment specific information, such as endpoints and passwords, for example, to be stored as environment variables on a server. They are also used to set the important directory locations for many popular packages, such as JAVA_HOME for Java.

Setting an Environment Variable

To set an environment variable the export command is used. We give the variable a name, which is what is used to access it in shell scripts and configurations and then a value to hold whatever data is needed in the variable.

For example, to set the environment variable for the home directory of a manual OpenJDK 11 installation, we would use something similar to the following.

export JAVA_HOME=/opt/openjdk11

To output the value of the environment variable from the shell, we use the echo command and prepend the variable’s name with a dollar ($) sign.

And so long as the variable has a value it will be echoed out. If no value is set then an empty line will be displayed instead.

Unsetting an Environment Variable

To unset an environment variable, which removes its existence all together, we use the unset command. Simply replace the environment variable with an empty string will not remove it, and in most cases will likely cause problems with scripts or application expecting a valid value.

To following syntax is used to unset an environment variable

For example, to unset the JAVA_HOME environment variable, we would use the following command.

Listing All Set Environment Variables

To list all environment variables, we simply use the set command without any arguments.

An example of the output would look something similar to the following, which has been truncated for brevity.

BASH=/bin/bash BASHOPTS=checkwinsize:cmdhist:complete_fullquote:expand_aliases:extglob:extquote:force_fignore:globasciiranges:histappend:interactive_comments:login_shell:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=([0]="0") BASH_ARGV=() BASH_CMDS=() BASH_COMPLETION_VERSINFO=([0]="2" [1]="8") BASH_LINENO=() BASH_SOURCE=() BASH_VERSINFO=([0]="5" [1]="0" [2]="3" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu") BASH_VERSION='5.0.3(1)-release' COLUMNS=208 DIRSTACK=() EUID=1000 GROUPS=() HISTCONTROL=ignoreboth HISTFILE=/home/ubuntu/.bash_history HISTFILESIZE=2000 HISTSIZE=1000 HOME=/home/ubuntu HOSTNAME=ubuntu1904 HOSTTYPE=x86_64 IFS=$' \t\n' LANG=en_US.UTF-8 LESSCLOSE='/usr/bin/lesspipe %s %s' LESSOPEN='| /usr/bin/lesspipe %s' LINES=54

Persisting Environment Variables for a User

When an environment variable is set from the shell using the export command, its existence ends when the user’s sessions ends. This is problematic when we need the variable to persist across sessions.

To make an environment persistent for a user’s environment, we export the variable from the user’s profile script.

Open the current user’s profile into a text editor

export JAVA_HOME=/opt/openjdk11

Adding the environment variable to a user’s bash profile alone will not export it automatically. However, the variable will be exported the next time the user logs in.

To immediately apply all changes to bash_profile, use the source command.

Export Environment Variable

Export is a built-in shell command for Bash that is used to export an environment variable to allow new child processes to inherit it.

To export a environment variable you run the export command while setting the variable.

export MYVAR="my variable value"

We can view a complete list of exported environment variables by running the export command without any arguments.

SHELL=/bin/zsh SHLVL=1 SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.1pB5Pry8Id/Listeners TERM=xterm-256color TERM_PROGRAM=vscode TERM_PROGRAM_VERSION=1.48.2

To view all exported variables in the current shell you use the -p flag with export.

Setting Permanent Global Environment Variables for All Users

A permanent environment variable that persists after a reboot can be created by adding it to the default profile. This profile is loaded by all users on the system, including service accounts.

All global profile settings are stored under /etc/profile. And while this file can be edited directory, it is actually recommended to store global environment variables in a directory named /etc/profile.d, where you will find a list of files that are used to set environment variables for the entire system.

Create a new file under /etc/profile.d to store the global environment variable(s). The name of the should be contextual so others may understand its purpose. For demonstrations, we will create a permanent environment variable for HTTP_PROXY.

sudo touch /etc/profile.d/http_proxy.sh

sudo vi /etc/profile.d/http_proxy.sh

export HTTP_PROXY=http://my.proxy:8080

export HTTPS_PROXY=https://my.proxy:8080

export NO_PROXY=localhost. 1,.example.com

Conclusion

This tutorial covered how to set and unset environment variables for all Linux distributions, from Debian to Red Hat. You also learned how to set environment variables for a single user, as well as all users.

Источник

Where do I place commands to automatically be exported for all users?

I have an embedded platform running an Arago linux distribution. Right now the only «user» is root but there will eventually be others, but I don’t know how many or what user IDs they will have. Every user of this system must have a particular environment variable exported in order for the GUI to work correctly. I found that if I created and then added the export command to /home/root/.profile it is set correctly for root . Where should I place the command such that it is exported for every (current and future) user of the system? Note: On my system, at start up there were no files present in /home/root , I added .bash_profile but that didn’t work, then I added .profile and that did work. I thought I might have a dash shell because of that, but when I check /bin/sh it points to bash . so I tagged both.

@Eddy_Em — Thanks.. so /etc/bashrc doesn’t exist, but /etc/profile.d/ does. There’s a couple of shell scripts in there. I take it I just add another one that does an export and that will be autorun?

This isn’t an unambiguous way: user can delete needed lines from his ~/.bashrc . But you can replace bash by a script that will run bash with needed environment.

@terdon — That’s not a duplicate. That Question is how to get commands run for a specific user, which is why the Q and A’s are all talking about ~/.profile , that doesn’t solve my problem because I need this command done for all current and future users, which is why it needed to be done in the /etc/profile.d/ area

Источник