Too many levels of symbolic links when using ln to create soft links
[email protected]:/opt/jdk1.8.0_181/bin# ln-s Java /usr/local/bin/ Java
change to:
root @instancevgiv786y :/opt/jdk1.8.0_181/bin# ln-s /opt/jdk1.8.0_181/bin/ Java /usr/local/bin/ Java
Obviously I’m installing the JDK, but why would I want to create this soft connection?Just add the environment variable at /etc/profile. However, when I connected this server as one of Jenkins’ nodes, I was surprised to find that Java could not be found. Obviously, I added the environment variable and it took effect. Jenkins had to look under various bin directory, so I created this soft connection.
Read More:
- Install and uninstall under Linux system Node.js
- Jenkins docker push to harbor to report error
- Raspberry pie upgrade to Python 3.7.3
- Job for apache2.service failed apache2 cannot be started
- Error running docker container: starting container process caused “exec: \“python\“: executable file
- Copy node causes NPM execution error: cannot find module ‘/ / lib / utils/ unsupported.js ‘
- When Jenkins deploys the project, GIT reports an error fatal: index file smaller than expected
- Solve the problem of Python in Windows environment: Fatal error in launcher: Unable to create process using’”‘ in pip installation
- The python version output from the command line is inconsistent with the python version in the current CONDA environment
- CentOS solves the problem of modulenotfounderror when salt calls python3 script remotely, and solves the problem that PIP3 module cannot be shared by different users
- The Java command could not find or load the main class
- (Copy python package, the problem generated) pip Fatal error in launcher: Unable to create process using
- Installing and uninstalling nodejs in Linux
- Java was started but returned exit code = 13
- Jenkins series installation and deployment in docker mode
- ln: failed to create symbolic link ‘/usr/bin/pip’: File exists
- Jenkins git configuration error status code 128 ‘text file busy’
- Solve ssh error: shell request failed on channel 0
- Error running Eclipse: failed to load the JNI shared library
- Problem in configuring Maven error: Java_ HOME not found in your environment.