kloxo的安装和配置
[
2010/06/16 10:53 | by Totti ]
2010/06/16 10:53 | by Totti ]
Kloxo是一个优秀的Web控制面板，有商业版本和免费版本。免费版本的Kloxo允许绑定40个域名，对普通客户来讲 40个域名也足够用了。瑞豪开源的VPS提供了预装免费版Kloxo的Linux系统。本文介绍Kloxo控制面板的基本使用方法。
Directadmin配置
[ 2010/06/15 20:04 | by Totti ]
2010/06/15 20:04 | by Totti ]
配置保存记录
/usr/local/directadmin/scripts/setup.txt
/usr/local/directadmin/scripts/setup.txt
电信宽带到期后仍然收费
[ 2010/06/04 09:12 | by Totti ]
2010/06/04 09:12 | by Totti ]
电信宽带到期后一个月，要注销仍然要被收费，于是我把上海电信投诉到了工信部，没想到啊，问题还真解决了，问题解决了啊，胃口就好，身体倍儿棒，吃嘛嘛香！
大家被电信欺负的话，也到工信部网站投诉一下吧：
http://www.chinatcc.gov.cn:8080/cmsadmin/shouli/shensu.jsp
投诉全文：
大家被电信欺负的话，也到工信部网站投诉一下吧：
http://www.chinatcc.gov.cn:8080/cmsadmin/shouli/shensu.jsp
投诉全文：
引用
我09年办理的预付费包年套餐1M，于2010年4月30日到期，5月1日不能上网。
今天6月1日，因近期要离开上海，向上海电信咨询注销事宜，被告知，需要补交5月1日-30日的月租140元，才能申请注销，拆机。
我认为电信预付费套餐一年，那么合同有效期就是一年，到期后，在我没充值的情况下，不能使用宽带，就不会继续产生费用；而且在5月1日-30日，我也没有接到上海电信任何的电话通知，如果我不注销将会产生新的套餐费用。
对上海电信的这种处理方式，我觉得严重违反中华人民共和国合同法中“平等、自愿原则”的原则，因为合同到期后产生的费用，这是被续费，而且我在这个月也没享受到这个宽带使用。
上海电信网上QQ客服工号：工号******
我要求的处理：
办理注销、拆机业务，不需缴纳不合理的合同有效期之外的月租费用（2010年5月）。
希望工信部给我做主，消除中国电信这个不合理的收费项目！
今天6月1日，因近期要离开上海，向上海电信咨询注销事宜，被告知，需要补交5月1日-30日的月租140元，才能申请注销，拆机。
我认为电信预付费套餐一年，那么合同有效期就是一年，到期后，在我没充值的情况下，不能使用宽带，就不会继续产生费用；而且在5月1日-30日，我也没有接到上海电信任何的电话通知，如果我不注销将会产生新的套餐费用。
对上海电信的这种处理方式，我觉得严重违反中华人民共和国合同法中“平等、自愿原则”的原则，因为合同到期后产生的费用，这是被续费，而且我在这个月也没享受到这个宽带使用。
上海电信网上QQ客服工号：工号******
我要求的处理：
办理注销、拆机业务，不需缴纳不合理的合同有效期之外的月租费用（2010年5月）。
希望工信部给我做主，消除中国电信这个不合理的收费项目！
Ubuntu使用SSH代理设置
[ 2010/06/03 21:28 | by Totti ]
2010/06/03 21:28 | by Totti ]
ssh -qTfnN -D 7070 username@sshserver
eaccelerator 安装
[ 2010/06/01 16:37 | by Totti ]
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 ]
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.按官网的说明，支持绝大部分黑莓手机
