本文目录一览:
- 1、centos yum如何搜索库文件属于哪个包
- 2、如何给CentOS安装字体库?
- 3、安装centos下安装MYSQL数据库问题
- 4、centos中怎么删除mysql数据库
- 5、centos5.8用什么数据库
- 6、centos 7 安装什么数据库
centos yum如何搜索库文件属于哪个包
直接 rpm -qf 完整路径文件名。
若此文件未安装,例如安装1个rpm包但是提升缺少这个缺少那个的。
那有两个方法可以查
1.如果有RPM包在本地,可以使用
rpm -qpl .rpm file name
查询一个未安装的 RPM文件里所包含的文件
2.如果网络正常或者有yum本地源,可以使用
yum provides 文件名【可以携带通配符】
[root@edward ~]# yum provides *smbclient
Loaded plugins: downloadonly, fastestmirror, list-data, presto, security
Loading mirror speeds from cached hostfile
samba-client-3.5.10-125.el6.x86_64 : Samba client programs
Repo : base
Matched from:
Filename : /usr/bin/smbclient
它将会在源里查找这个文件属于哪个包。
如何给CentOS安装字体库?
如果各位读者向Linux.NET部署站点时遇到下面这幅图的时候,本文就恰好能够派上用场了,因为它正在提示您:您的操作系统缺少了相关的字体库\x0d\x0a\x0d\x0a 这时候,只需要参照本文一下的操作即可。\x0d\x0a 首先,第一步我们需要执行以下的命令来安装字体管理工具:\x0d\x0a yum install -y fontconfig mkfontscale\x0d\x0a 然后我们到“c:\windows\fonts”中把我们需要的字体拷贝出来(这里我们拷贝了“Arial”、“Comic Sans MS”、“Georgia”、“Times New Roman”四种)\x0d\x0a\x0d\x0a 把他们拷贝出来(注意,这里是字体的连带关系,你拷贝一个字体系统会把附属的也跟着拷贝出来,可以不用管)\x0d\x0a 然后上传到“/usr/share/fonts”\x0d\x0a \x0d\x0a 执行下面三条命令刷新字体缓存\x0d\x0a mkfontscale\x0d\x0a mkfontdir\x0d\x0a fc-cache -fv\x0d\x0a 最后重启操作系统(Reboot)\x0d\x0a 在这里,读者们可以执行“fc-list”来查看安装了那些字体(看每一个小段落前面的那加个英文即可)\x0d\x0a 好的,本节内容就到这里了,谢谢。
安装centos下安装MYSQL数据库问题
提示没有这个文件。看看是不是你进入的目录错了,或者下载的软件不对。
centos中怎么删除mysql数据库
查看已经安装的服务
rpm –qa|grep -i mysql
-i 作用是不区分大小写
yum remove mysql mysql-server mysql-libs compat-mysql51
rm -rf /var/lib/mysql
rm /etc/my.cnf
查看是否还有mysql软件:
rpm -qa|grep mysql
有的话继续删除
可以看到有两个安装包
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时输入只有两行:
[root @localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
Preparing… ########################################### [100%]
1:MySQL-server ########################################### [100%]
卸载干净了安装输入如下:
[root @localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
Preparing… ########################################### [100%]
1:MySQL-server ########################################### [100%]
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).
2014-09-23 07:22:43 26041 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-09-23 07:22:43 26041 [Note] InnoDB: The InnoDB memory heap is disabled
2014-09-23 07:22:43 26041 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-09-23 07:22:43 26041 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-09-23 07:22:43 26041 [Note] InnoDB: Using Linux native AIO
2014-09-23 07:22:43 26041 [Note] InnoDB: Using CPU crc32 instructions
2014-09-23 07:22:43 26041 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-09-23 07:22:43 26041 [Note] InnoDB: Completed initialization of buffer pool
2014-09-23 07:22:43 26041 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2014-09-23 07:22:43 26041 [Note] InnoDB: Database physically writes the file full: wait…
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2014-09-23 07:22:45 26041 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2014-09-23 07:22:45 26041 [Warning] InnoDB: New log files created, LSN=45781
2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer not found: creating new
2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer created
2014-09-23 07:22:45 26041 [Note] InnoDB: 128 rollback segment(s) are active.
2014-09-23 07:22:45 26041 [Warning] InnoDB: Creating foreign key constraint system tables.
2014-09-23 07:22:45 26041 [Note] InnoDB: Foreign key constraint system tables created
2014-09-23 07:22:45 26041 [Note] InnoDB: Creating tablespace and datafile system tables.
2014-09-23 07:22:45 26041 [Note] InnoDB: Tablespace and datafile system tables created.
2014-09-23 07:22:45 26041 [Note] InnoDB: Waiting for purge to start
2014-09-23 07:22:45 26041 [Note] InnoDB: 5.6.19 started; log sequence number 0
A random root password has been set. You will find it in ‘/root/.mysql_secret’.
2014-09-23 07:22:46 26041 [Note] Binlog end
2014-09-23 07:22:46 26041 [Note] InnoDB: FTS optimize thread exiting.
2014-09-23 07:22:46 26041 [Note] InnoDB: Starting shutdown…
2014-09-23 07:22:48 26041 [Note] InnoDB: Shutdown completed; log sequence number 1625977
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).
2014-09-23 07:22:48 26065 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-09-23 07:22:48 26065 [Note] InnoDB: The InnoDB memory heap is disabled
2014-09-23 07:22:48 26065 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-09-23 07:22:48 26065 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-09-23 07:22:48 26065 [Note] InnoDB: Using Linux native AIO
2014-09-23 07:22:48 26065 [Note] InnoDB: Using CPU crc32 instructions
2014-09-23 07:22:48 26065 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-09-23 07:22:48 26065 [Note] InnoDB: Completed initialization of buffer pool
2014-09-23 07:22:48 26065 [Note] InnoDB: Highest supported file format is Barracuda.
2014-09-23 07:22:48 26065 [Note] InnoDB: 128 rollback segment(s) are active.
2014-09-23 07:22:48 26065 [Note] InnoDB: Waiting for purge to start
2014-09-23 07:22:48 26065 [Note] InnoDB: 5.6.19 started; log sequence number 1625977
2014-09-23 07:22:48 26065 [Note] Binlog end
2014-09-23 07:22:48 26065 [Note] InnoDB: FTS optimize thread exiting.
2014-09-23 07:22:48 26065 [Note] InnoDB: Starting shutdown…
2014-09-23 07:22:50 26065 [Note] InnoDB: Shutdown completed; log sequence number 1625987
A RANDOM PASSWORD HAS BEEN SET FOR THE MySQL root USER !
You will find that password in ‘/root/.mysql_secret’.
You must change that password on your first connect,
no other statement but ‘SET PASSWORD’ will be accepted.
See the manual for the semantics of the ‘password expired’ flag.
Also, the account for the anonymous user has been removed.
In addition, you can run:
/usr/bin/mysql_secure_installation
which will also give you the option of removing the test database.
This is strongly recommended for production servers.
See the manual for more instructions.
Please report any problems at
The latest information about MySQL is available on the web at
Support MySQL by buying support/licenses at
New default config file was created as /usr/my.cnf and
will be used by default by the server when you start it.
You may edit this file to change server settings
最后一段中提示了重要信息,很多人因为不喜欢读英文,导致接下来不知道怎么操作!
二就是安装完成,启动服务之后
使用命令:“mysql -uroot -p”输入你之前安装后设置的密码,看能不能登录,如果还可以登录,说明没有卸载干净!
centos5.8用什么数据库
配mysql-4.1.22吧,
这是原始配置的数据库,
你也可以升级,
但是得注意依赖关系
centos 7 安装什么数据库
首先要确保电脑正常上网,才能通过yum安装。
2
执行yum install mysql进行安装。并在提示时输入y。
然后系统会自动寻找安装包,并进行安装。下图显示已成功安装完毕。
安装完毕后,尝试启动数据库。
系统提示找不到这个服务。再次看一下安装的包:
#rpm -qa |grep mysql
命令返回空,说明刚才没有安装成功。只好再次安装了。不过这次我们在命令后面加上*号。
看图,需要安装的包还真多!安装完成后,却发现只安装了JDBC和ODBC驱动。
我们在软件库中搜一下带mysql关键字的软件包:
返回的结果显示,软件库中根本就没有mysql软件包。这个时候,迷茫的开始查资料,资料显示在Centos7中用MariaDB代替了mysql数据库。好吧!那我们来安装MariaDB数据库吧!
操做方法同上,只不过在命令行里,把mysql改成了mariadb。
安装包一共59M
安装完成。
查看安装之后的包:
根据资料,mariadb数据库的启动命令是:
systemctl start mariadb #启动MariaDB
systemctl stop mariadb #停止MariaDB
systemctl restart mariadb #重启MariaDB
systemctl enable mariadb #设置开机启动
我执行以上命令,没有任何返回值。看来得研究一下mariadb数据了。
原创文章,作者:小蓝,如若转载,请注明出处:https://www.506064.com/n/249461.html