Home >System Tutorial >LINUX >Take stock of those Linux commands that are high-risk but have to be used
We have summarized and organized the high-risk commands of Linux here.
The article "Operation and Maintenance: Be respectful of data" summarizes how to avoid the risk of data loss from the main aspects of daily operation and maintenance. If you read carefully, you may realize that "the operating system level is definitely not only rm -rf" This type is related to files", so we have summarized and organized the high-risk commands of Linux here.
Based on the functions of operating system level commands, we divide high-risk commands into the following categories:
I believe that if we don’t sort it out carefully, we will never realize that there are so many types of high-risk commands, so let’s continue to look down!
Regarding the management of high-risk commands, we cannot disable them all "one size fits all", but must handle them differently according to their specific needs. Here are some of our suggestions.
For the processing of high-risk commands, we need to monitor and manage, which can be handled by combining the monitoring system and the bastion machine:
In fact, Linux high-risk commands do not only exist in simple command execution, but also widely exist in databases, application services, big data and other links that are closely related to the business. If our production server does not separate the permissions of development, operation and maintenance, and testers, then this summary of high-risk commands may come in handy.
The above is the detailed content of Take stock of those Linux commands that are high-risk but have to be used. For more information, please follow other related articles on the PHP Chinese website!