Sign In
Sign In

How to Set and Manage Linux Environment Variables

How to Set and Manage Linux Environment Variables
Umair Khurshid
Technical writer
Linux
03.04.2025
Reading time: 8 min

Environment variables are a core component of Linux, enabling users and system processes to store configuration values dynamically. They influence everything from command execution to system-wide settings, making them essential for both interactive sessions and automated processes.  

This guide explores setting and managing env variables, troubleshooting issues, securing sensitive data, and optimizing Linux systems through effective variable management. 

What Are Environment Variables?

An environment variable is a named value stored in system memory, affecting how processes behave. For example, when executing a command, the system references the PATH variable to locate the correct executable. 

To display all active variables:  

printenv

Image3

To retrieve a specific value:  

echo $HOME

51034b94 Bbd8 434d 875d 143e2f328b0e

There are two primary types of environment variables:  

  • Session-based: Exists only in the current terminal session.  
  • Persistent: Stored in configuration files to remain active after logout or reboot.  

Understanding how these variables function ensures smooth system operation and script automation.  

Setting Environment Variables

A temporary variable can be assigned using:  

export TEMP_VAR="Temporary Value"

To check if it was set:  

echo $TEMP_VAR

8b480279 C128 4ffe 854d 7a79e08d2b1d

This variable exists only in the current session. Once the shell is closed, it disappears.  

To create a persistent variable, append it to ~/.bashrc:  

echo 'export PERSISTENT_VAR="Stored Across Sessions"' >> ~/.bashrc && source ~/.bashrc

For system-wide settings, define variables in /etc/environment:  

echo 'GLOBAL_VAR="Available to All Users"' | sudo tee -a /etc/environment

A reboot or reloading the file ensures the changes take effect.  

Using Environment Variables in Shell Scripts

Scripts frequently rely on environment variables to pass configurations dynamically. Understanding their scope and behavior is key to avoiding unintended side effects.

Defining and Accessing Variables in Scripts

A variable can be defined within a script as follows:

#!/bin/bash
MY_VAR="Hello, World"
echo $MY_VAR

However, this variable exists only inside the script. Running it does not make MY_VAR available in the parent shell.

Exporting Variables for External Use

To make a variable accessible to child processes:

export GLOBAL_VAR="Persistent Value"
./my_script.sh

Da8131be E10c 4f20 87ee 7c82efcb5a31

Inside my_script.sh, the variable will be available. Without export, the script would not inherit the variable.

Sourcing a Script to Modify the Current Shell Environment

A script cannot modify the parent shell’s environment unless explicitly sourced:

source my_script.sh

or

. my_script.sh

C8f589d6 40db 411d A7e6 4de09fa28bca

This method is useful for setting persistent configurations dynamically.

Preventing Variable Collisions in Scripts

If multiple scripts use generic names like TEMP or DATA, unexpected conflicts can occur. Prefixing variables uniquely avoids this issue:

APP1_TEMP="value"
APP2_TEMP="value"

Alternatively, using local variables within functions prevents global namespace pollution:

my_function() {
    local TEMP_VALUE="Temporary Data"
    echo $TEMP_VALUE
}

By keeping variables properly scoped, script behavior remains predictable.

Managing Environment Variables in Cron Jobs

Cron jobs run on predefined schedules but operate in a minimal shell environment, often missing user-defined env variables. This leads to common issues when using variables inside cron scripts.

Unlike interactive shells, cron jobs do not load user profiles like ~/.bashrc or /etc/profile. Running a job that depends on custom variables may fail unless explicitly defined.

To check cron’s default environment:

env -i /bin/bash -c 'printenv'

Sdfvsdgv

This command runs a clean shell without inherited variables, mimicking cron behavior.

Defining Variables in Crontab

To ensure a variable is available in a cron job, define it within the crontab file:

MY_VAR="Scheduled Value"
* * * * * echo $MY_VAR >> /tmp/output.log

This approach works for simple variables but does not support complex setups.

Using an Environment File in Cron Jobs

For multiple variables, store them in a file and source it in the cron job:

* * * * * source /home/user/my_env_vars.sh && /home/user/my_script.sh

Alternatively, define the BASH_ENV variable to ensure the script loads the environment:

BASH_ENV="/home/user/my_env_vars.sh"
* * * * * /home/user/my_script.sh

This method ensures a consistent environment for all scheduled tasks.

Ensuring PATH Is Correctly Set

Many cron job failures occur due to an incomplete PATH. To prevent this, define it explicitly:

PATH="/usr/local/bin:/usr/bin:/bin"
* * * * * /home/user/my_script.sh

This avoids issues where commands work in a terminal but fail when run as a cron job.

Debugging Environment Variable Issues

If an env variable does not behave as expected, diagnosing the issue requires structured debugging.  

Confirming a Variable Is Set

To check if a variable exists:  

printenv VAR_NAME

If no output appears, the variable is unset or not exported.  

To verify if it exists only in the shell:  

set | grep VAR_NAME

Checking If a Variable Is Exported

A variable may be available in the current shell but not inherited by subprocesses. To check:  

bash -c 'echo $VAR_NAME'

If the output is empty, ensure the variable is exported:  

export VAR_NAME="Value"

Identifying Conflicting Variables

If a variable does not behave as expected, another definition may be overriding it. To locate all instances:  

grep VAR_NAME ~/.bashrc ~/.profile /etc/environment

If multiple definitions exist, remove any unintended ones.  

Testing Variables in a Clean Environment

To check if an issue is related to the shell configuration, launch a clean session and then, try setting and printing the variable again 

env -i bash --noprofile --norc

Using Environment Variables in Systemd Services

Many Linux services run as systemd units. Instead of defining env variables in shell scripts, systemd provides a structured way to manage them.  

To set env variables for a systemd service, create a drop-in configuration file:  

sudo mkdir -p /etc/systemd/system/my_service.service.d && echo -e "[Service]\nEnvironment=\"MY_VAR=MyValue\"" | sudo tee /etc/systemd/system/my_service.service.d/env.conf

Add the content and modify ExecStart as needed:

[Unit]
Description=My Custom Service
After=network.target

[Service]
ExecStart=/path/to/your/executable
Restart=always
Environment="MY_VAR=MyValue"

[Install]
WantedBy=multi-user.target

Reload systemd and restart the service:  

sudo systemctl daemon-reload
sudo systemctl restart my_service

To confirm that the variable was applied:  

sudo systemctl show my_service | grep MY_VAR

F7d8e096 C982 4833 8a3a 801183c55f1e

This method ensures that variables persist across reboots without modifying global shell configuration files.  

Environment Variables and Performance Optimization

Env variables affect performance by controlling system behavior at a fundamental level. Configuring them effectively can enhance efficiency and streamline resource management.

Optimizing Command Execution Paths

The PATH variable determines where the system looks for executables. If it contains unnecessary directories, command execution slows down. To optimize:  

export PATH="/usr/local/bin:/usr/bin:/bin"

Avoid overly long PATH values by removing redundant or unused paths.  

Reducing Memory Usage with LD_LIBRARY_PATH

Dynamic linking relies on the LD_LIBRARY_PATH variable. Setting unnecessary paths increases lookup time for shared libraries. Optimize by ensuring only required paths are included:  

export LD_LIBRARY_PATH="/usr/local/lib:/usr/lib"

Adjusting Process Priorities with OOM_SCORE_ADJ

The OOM_SCORE_ADJ variable influences how the Out-of-Memory (OOM) killer prioritizes processes for termination. For critical processes, reduce their likelihood of being killed:

echo -1000 | sudo tee /proc/$(pgrep my_critical_process)/oom_score_adj

Conversely, assign a high value to non-essential processes to allow them to be terminated first:

echo 500 | sudo tee /proc/$(pgrep background_task)/oom_score_adj

These optimizations improve system responsiveness under heavy loads.

Linux Hardening Through Environment Variable Management 

Improper use of env variables can expose sensitive information and create privilege escalation risks. Careful handling of these variables is essential, and using well-structured practices reduces potential risks.

Restricting Access to Configuration Files

Ensure that files storing env variables have restricted permissions:

chmod 600 ~/.bashrc ~/.profile

For system-wide files:

sudo chmod 644 /etc/environment

Preventing Path Manipulation Attacks

Malicious users can modify PATH to execute unintended commands. Instead of relying on cp file /backup/ always use absolute paths in scripts:

/usr/bin/cp file /backup/

Clearing Sensitive Variables

When handling credentials, remove them immediately after use:

unset API_KEY

This prevents them from being accessed through process listings or logs.

Wrapping Up

Linux environment variables are essential for configuring system behavior, optimizing performance, and ensuring security. By understanding how they work across different shells, debugging issues efficiently, and applying security best practices, users can create a more robust and efficient system.

The inclusion of systemd service configurations, performance optimizations, containerized environments, and Linux hardening techniques ensures a well-rounded approach to env variable management. Mastering these topics provides greater control over Linux-based systems and enhances both usability and security.

Linux
03.04.2025
Reading time: 8 min

Similar

Linux

How to Create a Text File in Linux Terminal

In Linux, you can access and edit text files using a text editor that is designed to work with plain text. These files are not specifically coded or formatted. Linux allows one to create a file in numerous ways. The fastest is, probably, Linux Command Line or Terminal. For all users—especially server administrators—who must rapidly generate text files, scripts, or configuration files for their work, this is a very important ability. Let's proceed to the guide on four standard techniques for creating a text file on the terminal. Prerequisites for File Creation in Linux Ensure these prerequisites are met before generating files in a Linux environment using the command-line interface: Access to a Functional Linux System: You must either have a Linux-based operating system installed on your computer or secure access to a Linux server via SSH (Secure Shell) protocol. Operational Terminal Interface: Confirm that your terminal application is accessible and fully operational. The terminal serves as your primary gateway to executing commands. Adequate User Permissions: Verify you can create files within the chosen directory. You may need to use sudo (for directories with access restrictions) to escalate privileges. Fundamental Commands Proficiency: You must get familiar with essential commands, such as touch for file creation, echo for printing text, cat for viewing file contents, and text editors like nano, vim, or vi for editing files directly. Text Editing Utilities: Ensure your system includes text editing tools: nano for command line simplicity, vim for advanced configurations, or graphical options like gedit for user-friendly navigation. Directory Management Expertise: Develop familiarity with directory navigation commands like cd for changing the working directory and ls for listing directory contents. This knowledge streamlines your workflow and avoids potential errors. Using the touch Command Generally, we use the touch command to create empty files and change timestamps. It will create an empty file if it doesn't exist already.  To create a text file in the current directory with the touch command: Open your terminal emulator. Type the command: touch filename.txt Change "filename" to your desired name. The timestamps for access and modification will be updated without changes in file content if the file exists already. Otherwise, an empty file is created with a given name.  Press Enter—if it is successful, there will be no output. Use the ls command to list the directory content and verify file creation. Using the echo Command Redirection The echo command is widely used to display text on the terminal. But its capabilities go beyond that; it may also be used to write content to a file or create an empty file. For this, combine the echo command with double redirect symbols (you can also use a single >) and the desired filename. A text file can be created by redirecting the output of the echo command to a file. See how it works: Open your terminal emulator. Type the command: echo “Your text content here” > filename.txt Replace the text in double quotations (do not delete them) with yours to add it to the file.  After you press Enter, your text will be added to the file filename.txt. It will overwrite an existing file, if there is one. Otherwise, it will just create a new one. Press Enter. To verify that the file has been created and contains the desired content, use cat command to display the content.  Using the cat Command Redirection In Linux, the cat command is mostly used to concatenate and show file contents. It can, however, also be used to generate a text document by redirecting the standard output of cat to a file. Open your terminal emulator. Type the following command: cat > filename.txt Replace filename.txt with the name for your text file. This command instructs cat to receive input rom the terminal and to redirect it into the filename.txt. Press Enter. The terminal will be waiting for input.  Enter the text you want in the file. Press Enter after each line. Press Ctrl + D when you are done. This signals the end of input to the cat and saves the content.  Run the cat command to check that the file has been created and contains the desired content. Start using Hostman efficient S3 storage Using printf for Advanced File Creation The printf utility is a powerful alternative to echo, offering enhanced formatting options for structuring text. It allows users to create files with precisely formatted content. Open the terminal. Use printf to define the text layout, incorporating formatting elements like newlines (\n) or tabs (\t). Redirect the output to a file using the > operator. Example: printf "First Line\nSecond Line\nIndented\tThird Line\n" >  formatted_file.txt Run the cat command to inspect the file's content and ensure the formatting matches expectations. Append Without Overwriting: To add content to an existing file without overwriting its current data, replace > with the append operator >>: printf "Additional content here.\n" >> formatted_file.txt Using a Text Dditor You can also create new files in linux text editors. There is always at least one integrated command-line text editor in your Linux distribution. But you can choose and install a different one according to your preferences, for example, Vim, Nano, or Emacs. Each of them has its own features and advantages. Vim vim, which stands for "Vi IMproved," is a very flexible and adaptable text editor. It is well-known for its modal editing, which allows for distinct modes for various functions like text entry, navigation, and editing. It allows split windows, multiple buffers, syntax highlighting, and a large selection of plugins for extra features. To create a text file using vim, follow the steps below: Open vim, with the desired filename as an argument. Press i to switch to Insert mode. Start typing and editing the filename.txt.  To save and exit, press Esc to ensure that command mode is running. Type: wq (write and quit) and press Enter. Nano nano is ideal for short adjustments and straightforward text files because it is lightweight and requires little setup. It provides support for basic text manipulation functions, search and replace, and syntax highlighting. To create a text file using nano, follow the steps below:  Run nano with the desired filename as an argument. It will open a new buffer for editing the file filename.txt. Start typing and editing the filename.txt.  To save and exit, press Ctrl + O to write the file, confirm the filename, and then press Ctrl + X to exit Nano. Emacs emacs is a powerful and flexible text editor that supports syntax highlighting, multiple buffers, split windows, and integration with external tools and programming languages. To create a text file using emacs, follow the steps below:  Open emacs, with the desired filename as an argument. Start typing and editing the filename.txt.  To save and exit, press Ctrl + X, followed by Ctrl + S to save the file, and then Ctrl + X, followed by Ctrl + C to exit Emacs. Note: If a message states that "VIM command not found", "nano command not found" or "emacs command not found" in Linux, it typically means that the vim, nano or emacs text editor is not installed on the system, or it's not included in the PATH environment variable, which is a list of directories where the operating system looks for executable files. To resolve this, install the text editor first using the command:  apt-get install vim apt-get install nano  apt-get install emacs Gedit An intuitive text editor that supports working with plain text and has syntax highlighting for programming languages. A straightforward graphical interface makes it usable for various tasks, from quick edits to complex document preparation. Open the Gedit Application: Launch Gedit either through the applications menu or by executing the following command in the terminal: gedit example.txt Gedit will create a new file if the specified one does not exist. Input Your Text: Type or paste your desired content into the editor. Save the File: Save your work with Ctrl + S or select File > Save. If creating a new file, specify a filename and a location. Verify: Return to the terminal and confirm the file exists with the ls command or review its content with cat. Linux File Creation Recommendations Ensure you have sufficient permissions to create files in the target directory. If they are insufficient, consider working in a directory where you have full rights (or elevate privileges with sudo). Check if a file with the identical name is already present before using the > operator, as the command will overwrite existing content. To prevent data loss, opt for the append operator >>. Familiarize yourself with the printf, echo, and text editors like vim or nano. These tools will help you reduce errors when working with files in Linux, as well as boost productivity. Use printf for creating files requiring structured content, such as configuration files or scripts with precise formatting needs. Conclusion Now you have acquainted yourself with the fundamental skill of creating a file in Linux using the terminal! Using the Linux command line, several fast and efficient methods exist to create and manage text files. Apply several techniques to meet a different requirement using the touch, echo, cat, printf commands, or text editors like vim, nano, gedit, or emacs. Users can select the method that sufficiently meets their requirements, such as creating empty files, appending text, or significantly modifying material. In summary, any of these methods enable Linux users to easily and quickly handle text files straight from the command line. Hostman offers a reliable managed Linux VPS for your projects.
21 April 2025 · 8 min to read
Linux

Installing and Configuring Grafana

Working with any IT project becomes much easier when the administrator has a wide range of metrics and monitoring data at their fingertips. It's even better when the data is presented in a clear and visual format. This is where tools like Grafana come in — an open-source solution designed to gather information from various sources and consolidate it into visual reports. Grafana supports multiple platforms — Windows, macOS, Linux (including popular distributions like Debian, Ubuntu, CentOS, Fedora, OpenSuse, or RedHat). It can work with databases such as SQLite, MySQL, and PostgreSQL. With so many options, administrators rarely need to adapt the solution to their environment. In this tutorial, we'll go over how to install Grafana, configure it, and work with dashboards. Installing Grafana on CentOS Stream When ordering a Linux VPS, users can install any Linux operating system. Usually, this is one of the common distributions like CentOS or Ubuntu. For this example, we'll assume the OS is already installed and ready for Grafana and other utility programs. Let's import the GPG keys: wget -q -O gpg.key https://rpm.grafana.com/gpg.key sudo rpm --import gpg.key Create a new official repository configuration: sudo nano /etc/yum.repos.d/grafana.repo Add the following content to the file: [grafana] name=grafana baseurl=https://rpm.grafana.com repo_gpgcheck=1 enabled=1 gpgcheck=1 gpgkey=https://rpm.grafana.com/gpg.key sslverify=1 sslcacert=/etc/pki/tls/certs/ca-bundle.crt Install the application: sudo dnf install grafana Enable autostart and launch Grafana: sudo systemctl enable grafana-server sudo systemctl start grafana-server Check the status to ensure Grafana is running: sudo systemctl status grafana-server You should see a message confirming that the service is loaded and active. This step is especially useful if someone previously worked with the server or installed a custom Linux build with bundled utilities. Installing Grafana on Ubuntu The process is similar: we install Grafana from the official repository after preparing the system to trust the source. Run these commands: wget -q -O - https://packages.grafana.com/gpg.key | sudo apt-key add - sudo add-apt-repository "deb https://packages.grafana.com/oss/deb stable main" sudo apt update sudo apt install grafana sudo systemctl enable grafana-server sudo systemctl start grafana-server sudo systemctl status grafana-server Firewall Configuration for Grafana By default, Grafana uses port 3000. Here's how to open it in different firewalls. For iptables: Add the rule: sudo iptables -A INPUT -p tcp --dport 3000 -m state --state NEW -j ACCEPT Save the rules so they persist after reboot: sudo service iptables save Restart iptables to apply changes: sudo systemctl restart iptables For firewalld: firewall-cmd --zone=public --add-port=3000/tcp --permanent systemctl reload firewalld Default Login and Password Grafana uses the default login/password: Username: admin Password: admin If forgotten, reset it with: grafana-cli admin reset-admin-password --homepath "/usr/share/grafana" new_password Data Sources and Plugin Installation Grafana supports numerous data sources: Prometheus, Graphite, OpenTSDB, InfluxDB, and more. It also allows plugin installations to enhance functionality. For example, to install the Zabbix plugin, run: grafana-cli plugins install alexanderzobnin-zabbix-app systemctl restart grafana-server After restart, go to Configuration > Plugins and find Zabbix. After you enable it, you can configure it under Data Sources. This same process applies to other plugins like Grafana PostgreSQL or Grafana Elasticsearch. Working with Grafana Dashboards The core of Grafana is dashboards — sets of panels that visually display data. Users can create their own dashboards by clicking New Dashboard and selecting panel types. Dashboard Types: Graph – multiple metrics in one panel. Stat – single metric graph. Gauge – speedometer-style display. Bar Gauge – vertical bar graph. Table – table with multiple metrics. Text – freeform text. Heatmap – heatmap display. Alert List – list of Grafana alerts. Dashboard List – list of favorite dashboards. You can also display logs from external sources using Grafana Logs, and export/import dashboards for reuse. For advanced control, refer to the official documentation. You can directly edit the grafana.ini file to change: Default ports Log storage paths Proxy settings User access controls Feature toggles Conclusion Grafana is a powerful and flexible monitoring solution. To fully unlock its potential, experiment with dashboards, try manual config via grafana.ini, and explore third-party plugins. As an actively developed project, Grafana remains one of the top data visualization and monitoring tools.
17 April 2025 · 4 min to read
Linux

How to Copy Files over SSH

The SSH (Secure Shell) protocol is a network protocol for remote command-line management of operating systems, widely considered the standard for remote access to *nix machines. It allows secure login to a server, remote command execution, file management (creating, deleting, copying, etc.), and more. Most cloud and hosting providers require SSH to access their services. In this article, we’ll look at how to copy files over SSH on both Windows and Linux systems. How SSH Works SSH can securely transmit any data (audio, video, application protocol data) through an encrypted communication channel. Unlike outdated and insecure protocols like Telnet and rlogin, SSH ensures data confidentiality and authenticity — essential for internet communications. Here’s how a secure connection between a client and server is established: TCP Connection Setup: By default, the server listens on port 22. Both sides share a list of supported algorithms (compression, encryption, key exchange) and agree on which to use. Authentication: To prevent impersonation, both parties verify each other's identities using asymmetric encryption (public/private key pairs). First, the server is authenticated. On the first connection, the client sees a warning with server details. Trusted server keys are stored in /home/<username>/.ssh/known_hosts. Key Generation: Once the server is verified, both sides generate a symmetric key to encrypt all data exchanged. User Authentication: This is done using either a password or a client-sent public key stored in /home/<username>/.ssh/authorized_keys on the server. The most popular implementation on Linux is OpenSSH, which comes pre-installed on most distributions (Ubuntu, Debian, RHEL-based, etc.). Clients like PuTTY or MobaXterm are used on Windows. Since Windows 10 and Server 2019, OpenSSH tools are also available natively. You can learn more about working with SSH in our tutorial. File Copying via SSH Two main utilities for copying files over SSH in Linux are scp and sftp. Both come with OpenSSH. SSH supports two protocol versions: 1 and 2. OpenSSH supports both, but version 1 is rarely used. Autocompletion Setup To enable Tab-based autocompletion when using scp, set up public key authentication: Generate a key pair: ssh-keygen You’ll see output like: Generating public/private rsa key pair. Enter file in which to save the key (/home/user/.ssh/id_rsa): Enter passphrase (empty for no passphrase): By default, your keys (id_rsa for private and id_rsa.pub for public) are saved to ~/.ssh/. Now copy the public key to the remote machine: ssh-copy-id [username]@[ip-address] After entering the user's password, you’ll see a message confirming the key was added. Secure Copy (SCP) For small data transfers (e.g., service configs), scp is best. Copy from local to remote: scp test.txt user@192.168.1.29:/home/user/ Copy multiple files: scp test1.txt test2.txt user@192.168.1.29:/home/user/ Copy from remote to local: scp user@192.168.1.29:/home/user/test.txt ~/ Copy directories: scp -r testdir user@192.168.1.29:/home/user/ Remote-to-remote copy: scp gendo@192.168.1.25:/home/gendo/test.txt user@192.168.1.29:/home/user/ Secure FTP (SFTP) SFTP is another utility included in OpenSSH. As of OpenSSH 9.0, scp now uses SFTP by default instead of the old SCP/RCP protocol. Unlike classic FTP, sftp transmits encrypted data over a secure tunnel. It does not require a separate FTP server. Example usage: sftp misato@192.168.1.29 sftp> ls sftp> lcd testdir/ sftp> get test.txt sftp> bye Graphical file managers like Midnight Commander and Nautilus use sftp. In Nautilus, the remote server appears like a local folder, e.g., user@ip. Copying Files Over SSH on Windows Use the pscp command-line tool from PuTTY to copy files on Windows. Copy to server: pscp C:\server\test.txt misato@192.168.1.29:/home/misato/ Copy from server: pscp misato@192.168.1.29:/home/misato/test.txt C:\file.txt List files on remote server: pscp -ls user@192.168.1.29:/home/misato Use quotes for paths with spaces: pscp "C:\dir\bad file name.txt" misato@192.168.1.29:/home/misato/ To get help, run: pscp Conclusion We’ve covered how to copy files to and from a server using the secure SSH protocol. If you work with cloud servers, understanding SSH is essential — it’s the standard method for remote access to *nix machines and a vital part of everyday DevOps and system administration.
14 April 2025 · 4 min to read

Do you have questions,
comments, or concerns?

Our professionals are available to assist you at any moment,
whether you need help or are just unsure of where to start.
Email us
Hostman's Support