How to solve the problem of command failure caused by overwriting the original PATH and prompting command not found

A colleague asked me to help him figure out why many commands on his LINUX server could not be used, with the prompt (command not found). What was even worse was that many system services and scripts could not be run. Let me ask you, what have you done before? He said that I did the same operation, just added export PATH in the /etc/profile file, and asked, how did you set it? The answer is:

[root@localhost ~]# vim /etc/profile 
export PATH=/usr/lib/jenkins/
[root@localhost ~]# source /etc/profile

He said that he just added the default working directory of Jenkins and then used source to make the configuration file effective. In fact, this is exactly where the problem lies!

PATH is the system environment path. All system commands and script executions are searched according to the PATH path. But if export PATH=/usr/lib/jenkins/ , all the directories set by the system before, such as (/bin/; /sbin and other directories storing system commands), will be overwritten and become jenkins work commands. System commands such as ls, pwd, cd will definitely not be found in the jenkins directory. As a result, all commands, scripts, and services will not be able to run. This is the main reason for this bloody incident!

How to set the real system PATH?

If it is a short-term setting:

export PATH=$PATH:/usr/lib/jenkins/

If it is a long-term setting:

[root@localhost ~]# vim /etc/profile 
export PATH=$PATH:/usr/lib/jenkins/
[root@localhost ~]# source /etc/profile

In this case, the new search path is added to the original setting without overwriting the original PATH.

Summarize

The above is the full content of this article. I hope that the content of this article will have certain reference learning value for your study or work. Thank you for your support of 123WORDPRESS.COM. If you want to learn more about this, please check out the following links