Be kind to the ubuntu server, don't do this!

Today, our front-end responded that the production environment could not be released.
Our front-end is a small-privileged user, the version issued by sftp. I immediately logged in to xshell and found that ssh could not be logged in either: Connection established, and then I immediately reported an error:
Connection closing...Socket close.

Checking the information, I saw http://www.mamicode.com/info-detail-2180109.html it said that the permission would change like this. I thought, it really seems that chmod 777 -R has been executed . . . Just because I forgot to add the path later. After finding that there was no movement for a long time, ctrl+c ended hastily.

Later, I submitted an Alibaba Cloud work order and asked the customer service to restart the solution. It turned out that I couldn't log in because of excessive permissions. I started the production environment in a hurry, and some services couldn't get up due to permission issues, and I was not proficient in starting some services. This time the production environment was paralyzed for more than half an hour, which was very serious.

If rm -rf / is an atomic bomb that destroys the world. The chmod 777-R that I saw today is an EMP weapon. It seems to have no harm to online services. In fact, it is no longer possible to log in. It will be a matter of time before restarting, and the permission issue after restarting is also slightly tricky.

Do not execute chmod 777 -R casually

Guess you like

Origin blog.csdn.net/u012452555/article/details/106151476