作者归档:John

解决Apache的Mod_Security和svn模块冲突

今天svn突然不能提交了,给777都没用,一直报错

Command: Commit
Error: Commit failed (details follow):
Error: access to ‘/!svn/vcc/default’ forbidden
Finished!:

Google了好一阵子,解决方案如下:

在svn对应的虚拟主机的</VirtualHost>之前插入这样一段

<IfModule mod_security2.c>
SecRuleRemoveByID 960032
SecRuleRemoveByID 960015
SecRuleRemoveByID 960904
SecRuleRemoveByID 960010
SecRuleRemoveByID 960035
SecRule REQUEST_METHOD “^(PROPFIND|PROPPATCH)$” allow
SecRule REQUEST_METHOD “^(REPORT|OPTIONS)$” allow
SecRule REQUEST_METHOD “^(MKACTIVITY|CHECKOUT)$” allow
SecRule REQUEST_METHOD “^(PUT|DELETE|MERGE)$” allow
SecRule REQUEST_METHOD “^(MKCOL)$” allow
</IfModule>

完成后重启apache就可以了。

原因:mod_security过于严格=。-

Google Apps即将对放弃.cn域名的支持

尊敬的Google企业应用套件管理员:

您好!我们联系您是因为您正在使用下面所列的.cn域名作为您Google企业应用套件服务 主域名的别名(alias)。Google目前并不在.cn域名下提供Google企业应用套件服务,包括.cn域名作为域名别名(alias)的服务。 遗憾的是由于我们注册流程上的疏漏,您的.cn域名被允许作为了Google企业应用套件服务的域名别名。

我们将会在格林威治时间(GMT)2011年1月10日18时删除您控制面板域名别名列表中的所有.cn域名。这个操作不会影响到您的用户的任何数据。

如果您希望继续收到发送到.cn域名的邮件,我们推荐您为.cn域名选择一个不同的邮件解决方案。您的其它非.cn域名的邮件服务将不受影响。

我们对工作疏漏导致的不便表示歉意。我们理解这次数据转移可能会给您带来不便,同时我们也致力于帮助您尽可能圆满的完成数据迁移。 如果您需要任何帮助,请直接回复本邮件,我们的团队会帮助您。如果您需要进一步的技术协助,请提供您的电话号码和两个方便的交流时间,我们会随后和您联 系。

祝顺利,

Google企业应用套件团队
1600 Amphitheatre Pkwy
Mountain View, CA, 94040
电子邮件接收设置:我们向您发送这封必读的电子邮件服务通告,目的是让您了解 Google Enterprise 产品或帐户的重大变化。

下面的.cn域名别名将会在格林威治时间(GMT)2011年1月10日18时被删除:
xxx.com: xxx.cn

Google Apps service change notification/关于Google企业应用套件服务的变更通知

Dear Google Apps admin,

We’re contacting you regarding your use of Google Apps with the domains listed below as a domain alias or aliases.  Google does not offer this product on .cn domains, including the use of .cn domains as domain aliases. Unfortunately, due to an error in our domain alias feature, your .cn domain was allowed as a domain alias.

On 10 January 2011 at 18:00 GMT, all .cn domains listed in the domain alias section of your control panel will be removed by our team. This action will not affect any existing data for any of your users.

If you would like to continue to receive email sent to accounts that belong to your .cn domain, we recommend securing a different email solution for your .cn domain. Email service for your non-.CN domain names will be unaffected.

We apologize for our mistake and the inconvenience caused by this change. We appreciate this transition may be disruptive, and are committed to helping you make it as smooth as possible.  If you require any assistance, please reply to this message so our team can help. Additionally, if you would like technical assistance via the phone, please provide your phone number and two convenient times when we can reach you.

Sincerely,

The Google Apps Team
1600 Amphitheatre Pkwy
Mountain View, CA, 94040

You have received this mandatory email service announcement to update you about important changes to your Google Enterprise product or account.

The following .cn domain aliases will be removed on 10 January 2011 at 18:00 GMT:
xxx.com: xxx.cn

小小的mod一下wordpress-让不是已发布的文章编辑页显示查看文章链接

嗯,标题很长,其实已经说清楚了这篇文章的内容了- –

注意,这种做法是不推荐的,更新wordpress后会丢失更改,有空我会做成插件。
why:在wordpress后台编辑的时候,如果一篇文章不是已发布状态,就不会显示查看文章的链接,比较烦,所以需要小小的改动一个文件
how:编辑~/wp-admin/edit-form-advanced.php,在第243行后新建一行,插入如下代码:

<a href=”<?php echo get_permalink( $_GET[‘post’] ); ?>”><?php _e(‘View Post’); ?></a>

result:

多级缓存架构相当的给力

Mon.itor.us的检测结果表明,我的烂博客首页加载速度已经稳定在100ms左右的- –
目前博客逻辑架构是这样的:
前端:squid,跑在直连网通的xeex网络后,硬件是个小vps,128内存,xen架构,2G/150G,6刀一个月
后端:nginx反代httpd,同时nginx做部分静态文件服务器,硬件同样是个小vps,256内存,openvz架构,25G/250G,4刀一个月
数据库:mysqld,跑在上面那个256内存的vps上。
整个架构:squid>nginx>httpd>mysqld
用ab跑100个并发测试打开1000次首页,10多秒钟就搞定,服务器负载最多时候到了1- –
monitorus检测结果:
Test HTTP johnliu.info_http
12:23 676 OK US
12:53 105 OK US
13:23 116 OK US
13:53 1052 OK US
14:23 766 OK US
14:53 98 OK US
15:23 89 OK US
参考:
www.google.com_http 29

ab结果:
Server Software: nginx/0.8.53
Server Hostname: johnliu.info
Server Port: 80

Document Path: /others/kuai_fan_yuan_quakkfan_chong_xin_fa_bu/
Document Length: 15534 bytes

Concurrency Level: 100
Time taken for tests: 19.676012 seconds
Complete requests: 1000
Failed requests: 980
(Connect: 0, Length: 980, Exceptions: 0)
Write errors: 0
Total transferred: 16043778 bytes
HTML transferred: 15577247 bytes
Requests per second: 50.82 [#/sec] (mean)
Time per request: 1967.601 [ms] (mean)
Time per request: 19.676 [ms] (mean, across all concurrent requests)
Transfer rate: 796.25 [Kbytes/sec] received

Connection Times (ms)
min mean[+/-sd] median max
Connect: 11 90 98.4 96 3011
Processing: 32 1787 1663.1 1327 9043
Waiting: 11 252 340.5 110 1906
Total: 62 1878 1642.5 1420 9060

Percentage of the requests served within a certain time (ms)
50% 1420
66% 1565
75% 1663
80% 1791
90% 5181
95% 6338
98% 7419
99% 7650
100% 9060 (longest request)