本文目錄一覽:
- 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/zh-tw/n/249461.html