


How to modify environment variables in Linux operating system
Method 1: Add variables to the /etc/profile file [Effective for all users (permanent)]
Use vi to add variables to the file /etc/profile file. This variable will be valid for all users under Linux and is "permanent".
To make the modification take effect immediately, you need to execute the following code
Copy the code The code is as follows:
# source /etc/profile
Method 2: Add variables to the .bash_profile file in the user directory [Effective for a single user (permanent)]
Use vi to add variables to the .bash_profile file in the user directory. Changes are only effective for the current user and are "permanent".
To make the modification take effect immediately, you need to execute the following code in the user directory
Copy the code The code is as follows:
# source .bash_profile
Method 3: Directly run the export command to define variables [valid only for the current shell (bash) (temporary)]
Directly use [export variable name= on the shell command line Variable value] defines a variable. This variable is only valid under the current shell (bash) or its subshell (bash). When the shell is closed, the variable will become invalid. When you open a new shell, there will be no such variable. You need to use needs to be redefined.
Method 4: Direct assignment
Enter
in the command line to copy the code. The code is as follows:
path=$path: /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/bin
Using this method is only valid for the current session, that is, whenever you log out or After logging out of the system, the path settings will become invalid.
Method Five: Modify the /ect/profile file
Add
Copy code at the end of the file The code is as follows:
export path =$path:/usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/bin
//Note: There cannot be any spaces on both sides of the "=" sign. This method is the best, unless
you forcefully modify the path value manually, otherwise it will not be changed.
Method 6: Modify the .bachrc/.bash_profile file
Add
Copy code at the end of the file The code is as follows:
export path=$path:/usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/bin
This method works for the current user. It will also become invalid when you log out of the system
Note: For methods 2 and 3, if you want the path to take effect, you must log in again. The following method can simplify the work: If /etc/profile is modified, then the editing is completed Then execute the source profile or execute the command ./profile path and the value of the path will take effect immediately. The principle of this method is to execute the /etc/profile shell script again. Note that it will not work if you use sh /etc/profile, because sh is executed in a subshell process, and even if the path changes, it will not be reflected in the current environment. , but source is executed in the current shell process, so we can see the path change.
The above is the detailed content of How to modify environment variables in Linux operating system. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

Starting an Nginx server requires different steps according to different operating systems: Linux/Unix system: Install the Nginx package (for example, using apt-get or yum). Use systemctl to start an Nginx service (for example, sudo systemctl start nginx). Windows system: Download and install Windows binary files. Start Nginx using the nginx.exe executable (for example, nginx.exe -c conf\nginx.conf). No matter which operating system you use, you can access the server IP

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

How to fix Nginx 403 Forbidden error? Check file or directory permissions; 2. Check .htaccess file; 3. Check Nginx configuration file; 4. Restart Nginx. Other possible causes include firewall rules, SELinux settings, or application issues.

The error log is located in /var/log/nginx (Linux) or /usr/local/var/log/nginx (macOS). Use the command line to clean up the steps: 1. Back up the original log; 2. Create an empty file as a new log; 3. Restart the Nginx service. Automatic cleaning can also be used with third-party tools such as logrotate or configured.
