CENTOS 卸载文件夹如何卸载centos

转载

jojo 2024-08-28 12:50:11

文章标签 CENTOS 卸载文件夹 mysql centos MySQL bc 文章分类 架构后端开发

CentOS下如何完全卸载MySQL？解决卸载不干净的问题

CentOS 6.5，MySQL：MySql 5.6

rpm安装的卸载问题，我觉得使用yum方式安装的如果遇到相同的问题也一样适用。

查看已经安装的服务
 
rpm –qa|grep -i mysql 
 
 -i 作用是不区分大小写
可以看到有两个安装包
 
MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
 MySQL-client-5.6.19-1.linux_glibc2.5.x86_64.rpm
 
删除这两个服务(去掉后缀)
 
rpm –e MySQL-client-5.6.19-1.linux_glibc2.5.x86_64
 rpm -e MySQL-server-5.6.19-1.linux_glibc2.5.x86_64 
 
查看残留的目录：
 whereis mysql
然后删除mysql目录：
 rm –rf /usr/lib64/mysql
 
删除相关文件：
 
rm –rf /usr/my.cnf
 rm -rf /root/.mysql_sercret 
 
最关键的：
 rm -rf /var/lib/mysql

如果这个目录如果不删除，再重新安装之后，密码还是之前的密码，不会重新初始化！

网上查了很久都没有文章提到这个，最后还是自己摸索找出来的。

卸载完成！怎么确定是不是真的卸载干净了呢？

一是看安装输出：

如果没有卸载干净，安装server时输入只有两行：

1. [root@localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm  
2. Preparing...                ########################################### [100%]  
3.    1:MySQL-server           ########################################### [100%]

卸载干净了安装输入如下：

1. [root@localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm  
2. Preparing...                ########################################### [100%]  
3.    1:MySQL-server           ########################################### [100%]  
4. 2014-09-23 07:22:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).  
5. 2014-09-23 07:22:43 26041 [Note] InnoDB: Using atomics to ref count buffer pool pages  
6. 2014-09-23 07:22:43 26041 [Note] InnoDB: The InnoDB memory heap is disabled  
7. 2014-09-23 07:22:43 26041 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins  
8. 2014-09-23 07:22:43 26041 [Note] InnoDB: Compressed tables use zlib 1.2.3  
9. 2014-09-23 07:22:43 26041 [Note] InnoDB: Using Linux native AIO  
10. 2014-09-23 07:22:43 26041 [Note] InnoDB: Using CPU crc32 instructions  
11. 2014-09-23 07:22:43 26041 [Note] InnoDB: Initializing buffer pool, size = 128.0M  
12. 2014-09-23 07:22:43 26041 [Note] InnoDB: Completed initialization of buffer pool  
13. 2014-09-23 07:22:43 26041 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!  
14. 2014-09-23 07:22:43 26041 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB  
15. 2014-09-23 07:22:43 26041 [Note] InnoDB: Database physically writes the file full: wait...  
16. 2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB  
17. 2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB  
18. 2014-09-23 07:22:45 26041 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0  
19. 2014-09-23 07:22:45 26041 [Warning] InnoDB: New log files created, LSN=45781  
20. 2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer not found: creating new  
21. 2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer created  
22. 2014-09-23 07:22:45 26041 [Note] InnoDB: 128 rollback segment(s) are active.  
23. 2014-09-23 07:22:45 26041 [Warning] InnoDB: Creating foreign key constraint system tables.  
24. 2014-09-23 07:22:45 26041 [Note] InnoDB: Foreign key constraint system tables created  
25. 2014-09-23 07:22:45 26041 [Note] InnoDB: Creating tablespace and datafile system tables.  
26. 2014-09-23 07:22:45 26041 [Note] InnoDB: Tablespace and datafile system tables created.  
27. 2014-09-23 07:22:45 26041 [Note] InnoDB: Waiting for purge to start  
28. 2014-09-23 07:22:45 26041 [Note] InnoDB: 5.6.19 started; log sequence number 0  
29. A random root password has been set. You will find it in '/root/.mysql_secret'.  
30. 2014-09-23 07:22:46 26041 [Note] Binlog end  
31. 2014-09-23 07:22:46 26041 [Note] InnoDB: FTS optimize thread exiting.  
32. 2014-09-23 07:22:46 26041 [Note] InnoDB: Starting shutdown...  
33. 2014-09-23 07:22:48 26041 [Note] InnoDB: Shutdown completed; log sequence number 1625977  
34.   
35.   
36. 2014-09-23 07:22:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).  
37. 2014-09-23 07:22:48 26065 [Note] InnoDB: Using atomics to ref count buffer pool pages  
38. 2014-09-23 07:22:48 26065 [Note] InnoDB: The InnoDB memory heap is disabled  
39. 2014-09-23 07:22:48 26065 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins  
40. 2014-09-23 07:22:48 26065 [Note] InnoDB: Compressed tables use zlib 1.2.3  
41. 2014-09-23 07:22:48 26065 [Note] InnoDB: Using Linux native AIO  
42. 2014-09-23 07:22:48 26065 [Note] InnoDB: Using CPU crc32 instructions  
43. 2014-09-23 07:22:48 26065 [Note] InnoDB: Initializing buffer pool, size = 128.0M  
44. 2014-09-23 07:22:48 26065 [Note] InnoDB: Completed initialization of buffer pool  
45. 2014-09-23 07:22:48 26065 [Note] InnoDB: Highest supported file format is Barracuda.  
46. 2014-09-23 07:22:48 26065 [Note] InnoDB: 128 rollback segment(s) are active.  
47. 2014-09-23 07:22:48 26065 [Note] InnoDB: Waiting for purge to start  
48. 2014-09-23 07:22:48 26065 [Note] InnoDB: 5.6.19 started; log sequence number 1625977  
49. 2014-09-23 07:22:48 26065 [Note] Binlog end  
50. 2014-09-23 07:22:48 26065 [Note] InnoDB: FTS optimize thread exiting.  
51. 2014-09-23 07:22:48 26065 [Note] InnoDB: Starting shutdown...  
52. 2014-09-23 07:22:50 26065 [Note] InnoDB: Shutdown completed; log sequence number 1625987  
53.   
54.   
55.   
56.   
57. A RANDOM PASSWORD HAS BEEN SET FOR THE MySQL root USER !  
58. You will find that password in '/root/.mysql_secret'.  
59.   
60. You must change that password on your first connect,  
61. no other statement but 'SET PASSWORD' will be accepted.  
62. See the manual for the semantics of the 'password expired' flag.  
63.   
64. Also, the account for the anonymous user has been removed.  
65.   
66. In addition, you can run:  
67.   
68.   /usr/bin/mysql_secure_installation  
69.   
70. which will also give you the option of removing the test database.  
71. This is strongly recommended for production servers.  
72.   
73. See the manual for more instructions.  
74.   
75. Please report any problems at http://bugs.mysql.com/  
76.   
77. The latest information about MySQL is available on the web at  
78.   
79.   http://www.mysql.com  
80.   
81. Support MySQL by buying support/licenses at http://shop.mysql.com  
82.   
83. New default config file was created as /usr/my.cnf and  
84. will be used by default by the server when you start it.  
85. Y

最后一段中提示了重要信息，很多人因为不喜欢读英文，导致接下来不知道怎么操作！

CENTOS 卸载文件夹如何卸载centos_MySQL

二就是安装完成，启动服务之后

使用命令：“mysql -uroot -p”输入你之前安装后设置的密码，看能不能登录，如果还可以登录，说明没有卸载干净！



yum方式安装的mysql

 1、yum remove mysql mysql-server mysql-libs compat-mysql51
 2、rm -rf /var/lib/mysql
 3、rm /etc/my.cnf

 查看是否还有mysql软件：
 rpm -qa|grep mysql
 如果存在的话，继续删除即可。

 rpm方式安装的mysql

 a）查看系统中是否以rpm包安装的mysql：
 [root@localhost opt]# rpm -qa | grep -i mysql
 MySQL-server-5.6.17-1.el6.i686
 MySQL-client-5.6.17-1.el6.i686 b)卸载mysql
 [root@localhost local]# rpm -e MySQL-server-5.6.17-1.el6.i686
 [root@localhost local]# rpm -e MySQL-client-5.6.17-1.el6.i686

 c)删除mysql服务
 [root@localhost local]# chkconfig --list | grep -i mysql
 [root@localhost local]# chkconfig --del mysql

 d)删除分散mysql文件夹
 [root@localhost local]# whereis mysql 或者 find / -name mysql

 mysql: /usr/lib/mysql /usr/share/mysql

 清空相关mysql的所有目录以及文件
 rm -rf /usr/lib/mysql
 rm -rf /usr/share/mysql
 rm -rf /usr/my.cnf

 通过以上几步，mysql应该已经完全卸载干净了。
原文来自：

附录：
find / -name mysql  查找mysql文件夹
find / -name *mysql* 查找带有mysql的文件

本文章为转载内容，我们尊重原作者对文章享有的著作权。如有内容错误或侵权问题，欢迎原作者联系我们进行内容更正或删除文章。