忘記mysql root 密碼時可依下列方式修改:
[root@zabbix domo]# service mysqld stop //停止mysql
141004 20:20:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
正在停止 mysqld: [ 確定 ]
[root@zabbix domo]# mysqld_safe --skip-grant-tables & //用此指令進入安全模式跳過檢查權限的資料表
[1] 3154
[root@zabbix domo]# 141004 20:21:33 mysqld_safe Logging to '/var/log/mysqld.log'.
141004 20:21:33 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
[root@zabbix domo]# mysql -u root // 可用空密碼進入mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.1.73 Source distribution
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> update mysql.user set password=PASSWORD("mysql") where User='root'; //用此指令修改 root 密碼為mysql
Query OK, 0 rows affected (0.00 sec)
Rows matched: 3 Changed: 0 Warnings: 0
mysql> flush privileges; //刷新MySQL的系統許可權
Query OK, 0 rows affected (0.00 sec)
mysql> quit
Bye
[root@zabbix domo]# service mysqld start
正在啟動 mysqld: [ 確定 ]
可成功使用新密碼登入mysql
-----------------------------------------------------------
[root@zabbix domo]# mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 5.1.73 Source distribution
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| test |
+--------------------+
3 rows in set (0.01 sec)
mysql>
2014年10月4日 星期六
2014年10月3日 星期五
skype 找不倒網路攝影機,原來是VIrtual web cam 搞的鬼
同事的skype突然找不到筆電的網路攝影機,但是測試其他軟體攝影機是正常的,找了半天原來是ASUS 筆電的 ASUS virtual Camera造成的,把ASUS Utility"->"ASUS Virtual Webcam" 關掉後就正常了,下次若遇相同到問題可能也是類似的軟體造成的。
2014年9月27日 星期六
寄郵件時被退信常見的錯誤代碼
常遇到寄信時被退信,經由退信的錯誤代碼可大概判斷問題出在哪,整理網路上查到的DSN(Delivery Status Notification)資料方便判斷
標準格式為#x.y.z,x、y、z為阿拉伯數字
2.X.X:2表示成功
4.X.X:4表示有問題,但可能是短暫性故障,時好時壞。
5.X.X:5表示永久性的問題,需要經過設定或調整處理才能正常運作
DSN的第二碼
1:表示Addressing Status
2:表示Mailbox Status
3:表示Mail System Status
4:表示Network and Routing Status
5:表示Mail Delivery Protocol Status
6:表示Message Content or Media Status
7:表示Security or Policy Status
X.1.0 Other address status
X.1.1 Bad destination mailbox address
X.1.2 Bad destination system address
X.1.3 Bad destination mailbox address syntax
X.1.4 Destination mailbox address ambiguous
X.1.5 Destination mailbox address valid
X.1.6 Mailbox has moved
X.1.7 Bad sender's mailbox address syntax
X.1.8 Bad sender's system address
X.2.0 Other or undefined mailbox status
X.2.1 Mailbox disabled, not accepting messages
X.2.2 Mailbox full
X.2.3 Message length exceeds administrative limit
X.2.4 Mailing list expansion problem
X.3.0 Other or undefined mail system status
X.3.1 Mail system full
X.3.2 System not accepting network messages
X.3.3 System not capable of selected features
X.3.4 Message too big for system
X.4.0 Other or undefined network or routing status
X.4.1 No answer from host
X.4.2 Bad connection
X.4.3 Routing server failure
X.4.4 Unable to route
X.4.5 Network congestion
X.4.6 Routing loop detected
X.4.7 Delivery time expired
X.5.0 Other or undefined protocol status
X.5.1 Invalid command
X.5.2 Syntax error
X.5.3 Too many recipients
X.5.4 Invalid command arguments
X.5.5 Wrong protocol version
X.6.0 Other or undefined media error
X.6.1 Media not supported
X.6.2 Conversion required and prohibited
X.6.3 Conversion required but not supported
X.6.4 Conversion with loss performed
X.6.5 Conversion failed
X.7.0 Other or undefined security status
X.7.1 Delivery not authorized, message refused
X.7.2 Mailing list expansion prohibited
X.7.3 Security conversion required but not possible
X.7.4 Security features not supported
X.7.5 Cryptographic failure
X.7.6 Cryptographic algorithm not supported
X.7.7 Message integrity failure
常見問題:
#4.3.1
硬碟空間不足
#4.3.2
由管理者主動從Exchange System Manager的SMTP Virtual Server Queue中退回信件
#4.4.1
對方主機沒有反應,通常是由網路傳輸所造成的錯誤,系統會再主動重試多次
#4.4.2
Connection已經被中斷,通常是由於網路問題造成,或者是對方mail server已經Down了
#4.4.6
是指信件傳送已經超過了SMTP所設的最大Hop Count
應檢查是否Routing或某些設定造成loop
#4.4.7
是指超過傳送限件的期限,經常發生於對方限制接收信件的Recipient數或者某些通訊協定造成Time Out
#5.0.0
SMTP Address Space沒有可Route的對象
DNS查詢不到欲傳送的主機記錄
Routing Group之間沒有設Messaging Connector
SMTP Protocol錯誤
#5.1.0
如聯絡人未設e-mail位址
Outlook 將信件存成一個檔,然後在離線狀態下打開並且回覆信件
#5.1.1
E-Mail位址不存在於對方的組織中
#5.1.3
沒有e-mail位址型態
#5.1.4
兩個物件有兩個相同的e-mail位址
#5.2.3
超過己方Exchange 2000伺服器限制的大小容量
#5.3.3
通常是由於使用BDAT指令傳送,而對方的SMTP伺服器的硬碟空間不夠所致
#5.4.0
查詢DNS沒有發現 Authoritative host記錄
Smarthost 指定錯誤
FQDN 名稱存在於 HOSTS file (fixed in W2K SP3)
DNS 失效
SMTP Virtual Server沒有一個有效的FQDN
無效或沒有SMTP address spaces
#5.7.1
沒有反解IP
被列入IP黑名單而遭拒絕
被SMTP Connector限制寄出
Mail relay限制,經常發生於Outlook Express使用SMTP寄信時.
標準格式為#x.y.z,x、y、z為阿拉伯數字
2.X.X:2表示成功
4.X.X:4表示有問題,但可能是短暫性故障,時好時壞。
5.X.X:5表示永久性的問題,需要經過設定或調整處理才能正常運作
DSN的第二碼
1:表示Addressing Status
2:表示Mailbox Status
3:表示Mail System Status
4:表示Network and Routing Status
5:表示Mail Delivery Protocol Status
6:表示Message Content or Media Status
7:表示Security or Policy Status
X.1.0 Other address status
X.1.1 Bad destination mailbox address
X.1.2 Bad destination system address
X.1.3 Bad destination mailbox address syntax
X.1.4 Destination mailbox address ambiguous
X.1.5 Destination mailbox address valid
X.1.6 Mailbox has moved
X.1.7 Bad sender's mailbox address syntax
X.1.8 Bad sender's system address
X.2.0 Other or undefined mailbox status
X.2.1 Mailbox disabled, not accepting messages
X.2.2 Mailbox full
X.2.3 Message length exceeds administrative limit
X.2.4 Mailing list expansion problem
X.3.0 Other or undefined mail system status
X.3.1 Mail system full
X.3.2 System not accepting network messages
X.3.3 System not capable of selected features
X.3.4 Message too big for system
X.4.0 Other or undefined network or routing status
X.4.1 No answer from host
X.4.2 Bad connection
X.4.3 Routing server failure
X.4.4 Unable to route
X.4.5 Network congestion
X.4.6 Routing loop detected
X.4.7 Delivery time expired
X.5.0 Other or undefined protocol status
X.5.1 Invalid command
X.5.2 Syntax error
X.5.3 Too many recipients
X.5.4 Invalid command arguments
X.5.5 Wrong protocol version
X.6.0 Other or undefined media error
X.6.1 Media not supported
X.6.2 Conversion required and prohibited
X.6.3 Conversion required but not supported
X.6.4 Conversion with loss performed
X.6.5 Conversion failed
X.7.0 Other or undefined security status
X.7.1 Delivery not authorized, message refused
X.7.2 Mailing list expansion prohibited
X.7.3 Security conversion required but not possible
X.7.4 Security features not supported
X.7.5 Cryptographic failure
X.7.6 Cryptographic algorithm not supported
X.7.7 Message integrity failure
常見問題:
#4.3.1
硬碟空間不足
#4.3.2
由管理者主動從Exchange System Manager的SMTP Virtual Server Queue中退回信件
#4.4.1
對方主機沒有反應,通常是由網路傳輸所造成的錯誤,系統會再主動重試多次
#4.4.2
Connection已經被中斷,通常是由於網路問題造成,或者是對方mail server已經Down了
#4.4.6
是指信件傳送已經超過了SMTP所設的最大Hop Count
應檢查是否Routing或某些設定造成loop
#4.4.7
是指超過傳送限件的期限,經常發生於對方限制接收信件的Recipient數或者某些通訊協定造成Time Out
#5.0.0
SMTP Address Space沒有可Route的對象
DNS查詢不到欲傳送的主機記錄
Routing Group之間沒有設Messaging Connector
SMTP Protocol錯誤
#5.1.0
如聯絡人未設e-mail位址
Outlook 將信件存成一個檔,然後在離線狀態下打開並且回覆信件
#5.1.1
E-Mail位址不存在於對方的組織中
#5.1.3
沒有e-mail位址型態
#5.1.4
兩個物件有兩個相同的e-mail位址
#5.2.3
超過己方Exchange 2000伺服器限制的大小容量
#5.3.3
通常是由於使用BDAT指令傳送,而對方的SMTP伺服器的硬碟空間不夠所致
#5.4.0
查詢DNS沒有發現 Authoritative host記錄
Smarthost 指定錯誤
FQDN 名稱存在於 HOSTS file (fixed in W2K SP3)
DNS 失效
SMTP Virtual Server沒有一個有效的FQDN
無效或沒有SMTP address spaces
#5.7.1
沒有反解IP
被列入IP黑名單而遭拒絕
被SMTP Connector限制寄出
Mail relay限制,經常發生於Outlook Express使用SMTP寄信時.
2014年9月26日 星期五
CentOS 7 MySQL 變成 MariaDB 了
CentOS 7 MySQL 變成 MariaDB 了
MariaDB 安裝方式
[root@localhost ~]# yum -y install mysql
[root@localhost ~]# yum -y install mariadb-server
設定作業系統啟動時,自動啟動服務
[root@localhost system]# systemctl enable mariadb
[root@localhost system]# systemctl start mariadb
用 status 檢查服務狀態
[root@localhost system]# systemctl status mariadb
[root@localhost system]# mysql
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 2
Server version: 5.5.37-MariaDB MariaDB Server
Copyright (c) 2000, 2014, Oracle, Monty Program Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> \q
Bye
[root@localhost system]#
測試
測試
[root@localhost ~]# mysql -u root -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 13
Server version: 5.5.37-MariaDB MariaDB Server
Copyright (c) 2000, 2014, Oracle, Monty Program Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> show databases;
+------------------------------+
| Database |
+------------------------------+
| information_schema |
| mysql |
| performance_schema |
MariaDB 安裝方式
[root@localhost ~]# yum -y install mysql
[root@localhost ~]# yum -y install mariadb-server
設定作業系統啟動時,自動啟動服務
[root@localhost system]# systemctl enable mariadb
[root@localhost system]# systemctl start mariadb
用 status 檢查服務狀態
[root@localhost system]# systemctl status mariadb
[root@localhost system]# mysql
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 2
Server version: 5.5.37-MariaDB MariaDB Server
Copyright (c) 2000, 2014, Oracle, Monty Program Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> \q
Bye
[root@localhost system]#
設定 root 的密碼
[root@localhost ~]# mysql_secure_installation
/usr/bin/mysql_secure_installation: line 379: find_mysql_client: command not found
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
Set root password? [Y/n]
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n]
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n]
... Success!
By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n]
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n]
... Success!
Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
[root@localhost ~]#
[root@localhost ~]# mysql_secure_installation
/usr/bin/mysql_secure_installation: line 379: find_mysql_client: command not found
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
Set root password? [Y/n]
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n]
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n]
... Success!
By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n]
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n]
... Success!
Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
[root@localhost ~]#
設定 資料庫 root 的密碼
[root@localhost ~]# mysql_secure_installation
/usr/bin/mysql_secure_installation: line 379: find_mysql_client: command not found
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
Set root password? [Y/n]
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n]
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n]
... Success!
By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n]
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n]
... Success!
Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
[root@localhost ~]#
[root@localhost ~]# mysql_secure_installation
/usr/bin/mysql_secure_installation: line 379: find_mysql_client: command not found
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
Set root password? [Y/n]
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n]
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n]
... Success!
By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n]
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n]
... Success!
Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
[root@localhost ~]#
測試
設定 資料庫 root 的密碼
[root@localhost ~]# mysql_secure_installation
/usr/bin/mysql_secure_installation: line 379: find_mysql_client: command not found
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
Set root password? [Y/n]
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n]
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n]
... Success!
By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n]
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n]
... Success!
Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
[root@localhost ~]#
[root@localhost ~]# mysql_secure_installation
/usr/bin/mysql_secure_installation: line 379: find_mysql_client: command not found
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
Set root password? [Y/n]
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n]
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n]
... Success!
By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n]
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n]
... Success!
Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
[root@localhost ~]#
測試
[root@localhost ~]# mysql -u root -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 13
Server version: 5.5.37-MariaDB MariaDB Server
Copyright (c) 2000, 2014, Oracle, Monty Program Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> show databases;
+------------------------------+
| Database |
+------------------------------+
| information_schema |
| mysql |
| performance_schema |
| test |
+------------------------------+
4 rows in set (0.00 sec)
MariaDB [(none)]> quit
Bye
[root@localhost ~]#
+------------------------------+
4 rows in set (0.00 sec)
MariaDB [(none)]> quit
Bye
[root@localhost ~]#
2014年9月20日 星期六
解決首頁被hao123綁架
開IE或Firefox時首頁首頁被更改成hao123,用了以前的各種方法IE回復預設值,檢查IE內容是否被加上123,和使用了Malwarebytes Anti-Malware...等移除軟件都沒用,後來在http://azo-edu.blogspot.tw/2014/08/hao123-qvodplayer.html 找到答案,我也有裝QVOD兇手應該是他,不過在C:\Program Files\QvodPlayer\和C:\Program Files (x86)\QvodPlayer都找不到QvodExtend 這個資料夾,後來發現他原來是放到C:\ProgramData 這個隱藏資料夾裡面了,更名重開機後刪除QvodExtend 資料夾,就移除hao123 首頁了。
2014年3月26日 星期三
Windows Printer Server上安裝32及64位元印表機驅動程式
Printer Server要同時要提供x86及x64的Client列印,要事前在列印伺服器上安裝這二個版本的驅動程式,當用戶端在連到這些印表機時,才會自動下載適合的版本驅動程式。
1. Windows 2003上是32位元,只有32位元版本的驅動程式。
2. 找到後64位元Driver下載並將檔案解壓縮至一個資料夾。
3. 找一台加入網域的Windows 7 X64系統,開啟列印管理介面。(列印管理在控制台內的系統管理工具裡),透列印管理介面連到Printer Server,點選印表機內容時,它會要求先安裝一次驅動程式至Client。在安裝驅動程式時選擇從碟片安裝,並且請將路徑指向步驟2解開的資料夾。
4. 點選一次印表機內容>共用>其他驅動程式,即可以透過以下的介面將Windows 2003上安裝X64版本的驅動程式。
1. Windows 2003上是32位元,只有32位元版本的驅動程式。
2. 找到後64位元Driver下載並將檔案解壓縮至一個資料夾。
3. 找一台加入網域的Windows 7 X64系統,開啟列印管理介面。(列印管理在控制台內的系統管理工具裡),透列印管理介面連到Printer Server,點選印表機內容時,它會要求先安裝一次驅動程式至Client。在安裝驅動程式時選擇從碟片安裝,並且請將路徑指向步驟2解開的資料夾。
4. 點選一次印表機內容>共用>其他驅動程式,即可以透過以下的介面將Windows 2003上安裝X64版本的驅動程式。
2014年3月25日 星期二
Enable Launch CSM讓ASUS 筆電能用光碟開機
現在Notebook 都附 Win8 想改成WIN7或者想用光碟開機時但怎麼樣都找不到光碟機開機的選項怎麼辦,這是因為現在的BIOS已改為EFI,可以在BIOS 啟用Legacy 每家板子設定不同,但都大同小異。
以ASUS Notebook X45V為例:
1.進入BIOS 在 Boot 標籤裡面把Launch CSM 改成 enable
2.在Security 標籤裡面 secure boot control 改成disable
3.按F10 存檔離開
4.開機後按ESC就可以看到光碟機在開機裝設備的選項中了
5.可以開始用光碟開機重裝了
註:Legacy就是舊的BIOS,而EFI是新的BIOS
以ASUS Notebook X45V為例:
1.進入BIOS 在 Boot 標籤裡面把Launch CSM 改成 enable
2.在Security 標籤裡面 secure boot control 改成disable
3.按F10 存檔離開
4.開機後按ESC就可以看到光碟機在開機裝設備的選項中了
5.可以開始用光碟開機重裝了
註:Legacy就是舊的BIOS,而EFI是新的BIOS
訂閱:
文章 (Atom)