Directadmin配置
[ 2010/06/15 20:04 | by Totti ]
配置保存记录
/usr/local/directadmin/scripts/setup.txt
/usr/local/directadmin/scripts/setup.txt
Ubuntu使用SSH代理设置
[ 2010/06/03 21:28 | by Totti ]
ssh -qTfnN -D 7070 username@sshserver
eaccelerator 安装
[ 2010/06/01 16:37 | by Totti ]
http://eaccelerator.net/wiki/InstallFromSource
When you have only one php install, it's safe to run these commands in the source directory:
phpize
./configure
make
The phpize and php-config are the ones that are in your path. When you have more then one php install or the phpize and php-config scripts aren't in your path then you should follow this procedure. This example has php installed in /opt/php, this is the path of the --prefix option given to the php configuration script.
export PHP_PREFIX="/opt/php"
$PHP_PREFIX/bin/phpize
./configure --enable-eaccelerator=shared --with-php-config=$PHP_PREFIX/bin/php-config
make
For more information about the options for the configure script you should read the CompileConfiguration page.
After compilation, there should be a "eaccelerator.so" file in the modules subdirectory of the eAccelerator source directory.
Step 2. Installing eAccelerator ¶
make install
This will copy the previously created eAccelerator binary to the php extension directory. When this command ends, it will print out the directory in which eAccelerator has been installed.
Step 3. Configuring eAccelerator ¶
eAccelerator can be installed both as Zend or PHP extension. When you install eAccelerator as a zend_extension you need to give the full path to the eaccelerator.so library.
If you have /etc/php.d directory, you should copy eaccelerator.ini to it and modify the default values. If not, you need to edit your php.ini file (usually /etc/php.ini).
To install as Zend extension:
zend_extension="/usr/lib/php4/eaccelerator.so"
eaccelerator.shm_size="16"
eaccelerator.cache_dir="/tmp/eaccelerator"
eaccelerator.enable="1"
eaccelerator.optimizer="1"
eaccelerator.check_mtime="1"
eaccelerator.debug="0"
eaccelerator.filter=""
eaccelerator.shm_max="0"
eaccelerator.shm_ttl="0"
eaccelerator.shm_prune_period="0"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="9"
If you use a thread safe build of PHP you must use "zend_extension_ts" instead of "zend_extension".
To install as PHP extension:
extension="eaccelerator.so"
eaccelerator.shm_size="16"
eaccelerator.cache_dir="/tmp/eaccelerator"
eaccelerator.enable="1"
eaccelerator.optimizer="1"
eaccelerator.check_mtime="1"
eaccelerator.debug="0"
eaccelerator.filter=""
eaccelerator.shm_max="0"
eaccelerator.shm_ttl="0"
eaccelerator.shm_prune_period="0"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="9"
Step 4. Creating cache directory
One last very important step is creating the cache directory that you configured in the previous step. The default value is /tmp/eaccelerator It's easy because it's writable to everyone, but it isn't very smart because on a lot of systems this directory is cleaned on reboot. A better place would be /var/cache/eaccelerator. Create the directory and make sure it's writable for the user eAccelerator runs under (usually the user which you webserver runs as).
A safe bet is making it world writable. A safer and cleaner way would be to change the owner of the directory to the same user PHP runs as (most of the time the same user as Apache or Lighttpd) and set 0644 permissions.
The lazy way:
mkdir /tmp/eaccelerator
chmod 0777 /tmp/eaccelerator
When you have only one php install, it's safe to run these commands in the source directory:
phpize
./configure
make
The phpize and php-config are the ones that are in your path. When you have more then one php install or the phpize and php-config scripts aren't in your path then you should follow this procedure. This example has php installed in /opt/php, this is the path of the --prefix option given to the php configuration script.
export PHP_PREFIX="/opt/php"
$PHP_PREFIX/bin/phpize
./configure --enable-eaccelerator=shared --with-php-config=$PHP_PREFIX/bin/php-config
make
For more information about the options for the configure script you should read the CompileConfiguration page.
After compilation, there should be a "eaccelerator.so" file in the modules subdirectory of the eAccelerator source directory.
Step 2. Installing eAccelerator ¶
make install
This will copy the previously created eAccelerator binary to the php extension directory. When this command ends, it will print out the directory in which eAccelerator has been installed.
Step 3. Configuring eAccelerator ¶
eAccelerator can be installed both as Zend or PHP extension. When you install eAccelerator as a zend_extension you need to give the full path to the eaccelerator.so library.
If you have /etc/php.d directory, you should copy eaccelerator.ini to it and modify the default values. If not, you need to edit your php.ini file (usually /etc/php.ini).
To install as Zend extension:
zend_extension="/usr/lib/php4/eaccelerator.so"
eaccelerator.shm_size="16"
eaccelerator.cache_dir="/tmp/eaccelerator"
eaccelerator.enable="1"
eaccelerator.optimizer="1"
eaccelerator.check_mtime="1"
eaccelerator.debug="0"
eaccelerator.filter=""
eaccelerator.shm_max="0"
eaccelerator.shm_ttl="0"
eaccelerator.shm_prune_period="0"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="9"
If you use a thread safe build of PHP you must use "zend_extension_ts" instead of "zend_extension".
To install as PHP extension:
extension="eaccelerator.so"
eaccelerator.shm_size="16"
eaccelerator.cache_dir="/tmp/eaccelerator"
eaccelerator.enable="1"
eaccelerator.optimizer="1"
eaccelerator.check_mtime="1"
eaccelerator.debug="0"
eaccelerator.filter=""
eaccelerator.shm_max="0"
eaccelerator.shm_ttl="0"
eaccelerator.shm_prune_period="0"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="9"
Step 4. Creating cache directory
One last very important step is creating the cache directory that you configured in the previous step. The default value is /tmp/eaccelerator It's easy because it's writable to everyone, but it isn't very smart because on a lot of systems this directory is cleaned on reboot. A better place would be /var/cache/eaccelerator. Create the directory and make sure it's writable for the user eAccelerator runs under (usually the user which you webserver runs as).
A safe bet is making it world writable. A safer and cleaner way would be to change the owner of the directory to the same user PHP runs as (most of the time the same user as Apache or Lighttpd) and set 0644 permissions.
The lazy way:
mkdir /tmp/eaccelerator
chmod 0777 /tmp/eaccelerator
MidpSSH——移动SSH客户端软件
[ 2010/06/01 09:10 | by Totti ]
MidpSSH是一SSH和Telnet客户端软件,可运行于MIDP 1.0 / 2.0 (J2ME) 设备上,例如 Java兼容的手机或其它移动设备等。MidpSSH 基于GPL发布,网址 www.xk72.com。
MidpSSH支持 SSH1,Telnet和VT320 终端模拟,1.2+ 包括加密算法,支持SSH2 key交换。最新版本1.6支持键盘交互和代理服务器。
MidpSSH的作用
在移动终端上提供SSH和Telnet。对那些在任何地方需要登陆服务器的特别方便,不再需要找一台可以上网的电脑。需要指出的是,因为一般移动终端屏幕较小,连接也比较慢,所以不适合持久使用。
安装
可以通过http://xk72.com/wap直接上网下载安装,或者管理器安装
P.S.按官网的说明,支持绝大部分黑莓手机
MidpSSH支持 SSH1,Telnet和VT320 终端模拟,1.2+ 包括加密算法,支持SSH2 key交换。最新版本1.6支持键盘交互和代理服务器。
MidpSSH的作用
在移动终端上提供SSH和Telnet。对那些在任何地方需要登陆服务器的特别方便,不再需要找一台可以上网的电脑。需要指出的是,因为一般移动终端屏幕较小,连接也比较慢,所以不适合持久使用。
安装
可以通过http://xk72.com/wap直接上网下载安装,或者管理器安装
P.S.按官网的说明,支持绝大部分黑莓手机
使用 linux crontab命令 定时重启apache和mysql
[ 2010/05/28 17:16 | by Totti ]
服务器不重启的情况下定时自动重启apache及mysql服务,其实也大同小异。具体步骤如下:
一、每天的12点及16点重启apache及mysql服务
[root@www bin]# cd /opt/
[root@www opt]# vim reboot.txt
在reboot.txt.txt文件中输入下面的内容后保存
0 12 * * * service httpd restart
0 12 * * * service mysqld restart
0 16 * * * service httpd restart
0 16 * * * service mysqld restart
二、把新建的文件加入到cron服务中
[root@www opt]# crontab reboot.txt
[root@www opt]# crontab -l
0 12 * * * service httpd restart
0 12 * * * service mysqld restart
0 16 * * * service httpd restart
0 16 * * * service mysqld restart
一、每天的12点及16点重启apache及mysql服务
[root@www bin]# cd /opt/
[root@www opt]# vim reboot.txt
在reboot.txt.txt文件中输入下面的内容后保存
0 12 * * * service httpd restart
0 12 * * * service mysqld restart
0 16 * * * service httpd restart
0 16 * * * service mysqld restart
二、把新建的文件加入到cron服务中
[root@www opt]# crontab reboot.txt
[root@www opt]# crontab -l
0 12 * * * service httpd restart
0 12 * * * service mysqld restart
0 16 * * * service httpd restart
0 16 * * * service mysqld restart
directadmin my.conf的优化配置建议
[ 2010/05/28 16:16 | by Totti ]
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
skip-locking
#skip-networking
safe-show-database
query_cache_limit=1M
query_cache_size=64M ## 32MB for every 1GB of RAM
query_cache_type=1
max_user_connections=200
max_connections=500
interactive_timeout=10
wait_timeout=20
connect_timeout=20
thread_cache_size=128
key_buffer=128M ## 64MB for every 1GB of RAM
join_buffer=1M
max_connect_errors=20
max_allowed_packet=16M
table_cache=1024
record_buffer=1M
sort_buffer_size=2M ## 1MB for every 1GB of RAM
read_buffer_size=2M ## 1MB for every 1GB of RAM
read_rnd_buffer_size=2M ## 1MB for every 1GB of RAM
thread_concurrency=2 ## Number of CPUs x 2
myisam_sort_buffer_size=64M
server-id=1
log_slow_queries=/var/log/mysql-slow-queries.log
long_query_time=2
collation-server=latin1_general_ci
old-passwords
[mysql.server]
user=mysql
basedir=/var/lib
[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/lib/mysql/mysql.pid
open_files_limit=8192
[mysqldump]
quick
max_allowed_packet=16M
[mysql]
no-auto-rehash
#safe-updates
[isamchk]
key_buffer=32M
sort_buffer=32M
read_buffer=16M
write_buffer=16M
[myisamchk]
key_buffer=32M
sort_buffer=32M
read_buffer=16M
write_buffer=16M
[mysqlhotcopy]
interactive-timeout
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
skip-locking
#skip-networking
safe-show-database
query_cache_limit=1M
query_cache_size=64M ## 32MB for every 1GB of RAM
query_cache_type=1
max_user_connections=200
max_connections=500
interactive_timeout=10
wait_timeout=20
connect_timeout=20
thread_cache_size=128
key_buffer=128M ## 64MB for every 1GB of RAM
join_buffer=1M
max_connect_errors=20
max_allowed_packet=16M
table_cache=1024
record_buffer=1M
sort_buffer_size=2M ## 1MB for every 1GB of RAM
read_buffer_size=2M ## 1MB for every 1GB of RAM
read_rnd_buffer_size=2M ## 1MB for every 1GB of RAM
thread_concurrency=2 ## Number of CPUs x 2
myisam_sort_buffer_size=64M
server-id=1
log_slow_queries=/var/log/mysql-slow-queries.log
long_query_time=2
collation-server=latin1_general_ci
old-passwords
[mysql.server]
user=mysql
basedir=/var/lib
[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/lib/mysql/mysql.pid
open_files_limit=8192
[mysqldump]
quick
max_allowed_packet=16M
[mysql]
no-auto-rehash
#safe-updates
[isamchk]
key_buffer=32M
sort_buffer=32M
read_buffer=16M
write_buffer=16M
[myisamchk]
key_buffer=32M
sort_buffer=32M
read_buffer=16M
write_buffer=16M
[mysqlhotcopy]
interactive-timeout
Centos 上安装kloxo
[ 2010/05/19 12:22 | by Totti ]
CentOS是附带了httpd的unix版本,安装需要干净的系统,所以在装之前要反安装 httpd,php,mysql这些web组件。
yum remove httpd* php* mysql* -y
确定防火墙开启了7778和7777端口,以便打开kloxo。
Make sure that you open the ports 7778 and 7777 in the firewall. Otherwise you won't be able to connect to kloxo.
vi /etc/sysconfig/selinux 编辑,设置selinux=disabled,重启
You have to disable selinux by editing /etc/sysconfig/selinux and changing the line to selinux=disabled and then running
参考文档:http://wiki.lxcenter.org/Kloxo+Installation+Guide
命令:
# $ wget http://download.lxcenter.org/download/kloxo/production/kloxo-installer.sh
# $ sh ./kloxo-installer.sh --type=master
Centso下安装Kloxo出现YUM Gave Error… Trying Again的解决办法
Harry 3/20/2014 3:55:05 PM
在Centos下载安装Kloxo ,在安装过程中有可能出现YUM Gave Error… Trying Again 这样的错误,
发生这个错误的原因有3种
1,使用了64位的centos安装kloxo
2,使用了centos 6或者6以上版本安装kloxo (Kloxo 目前只能运行在 32 位的 CentOS 5或者5.X)
3,上面两则都不是但是还是出现错误:大多情况是kloxo安装到一半失败了,继续重装出现这个错误,出现这个错误的原因是:kloxo安装到一半的时候/etc/php.ini已被做了一些安装设置禁用了system这个函数。
解决方法:/etc/php.ini 里面找到 disable_functions 那几行全部注释掉就是在前面加一个分号。
然后重装开始安装kloxo就行了。
yum remove httpd* php* mysql* -y
确定防火墙开启了7778和7777端口,以便打开kloxo。
Make sure that you open the ports 7778 and 7777 in the firewall. Otherwise you won't be able to connect to kloxo.
vi /etc/sysconfig/selinux 编辑,设置selinux=disabled,重启
You have to disable selinux by editing /etc/sysconfig/selinux and changing the line to selinux=disabled and then running
参考文档:http://wiki.lxcenter.org/Kloxo+Installation+Guide
命令:
# $ wget http://download.lxcenter.org/download/kloxo/production/kloxo-installer.sh
# $ sh ./kloxo-installer.sh --type=master
Centso下安装Kloxo出现YUM Gave Error… Trying Again的解决办法
Harry 3/20/2014 3:55:05 PM
在Centos下载安装Kloxo ,在安装过程中有可能出现YUM Gave Error… Trying Again 这样的错误,
发生这个错误的原因有3种
1,使用了64位的centos安装kloxo
2,使用了centos 6或者6以上版本安装kloxo (Kloxo 目前只能运行在 32 位的 CentOS 5或者5.X)
3,上面两则都不是但是还是出现错误:大多情况是kloxo安装到一半失败了,继续重装出现这个错误,出现这个错误的原因是:kloxo安装到一半的时候/etc/php.ini已被做了一些安装设置禁用了system这个函数。
解决方法:/etc/php.ini 里面找到 disable_functions 那几行全部注释掉就是在前面加一个分号。
然后重装开始安装kloxo就行了。