<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ls /proc</title>
	<atom:link href="http://www.lsproc.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lsproc.com/blog</link>
	<description>lsproc.com</description>
	<lastBuildDate>Mon, 08 Mar 2010 03:45:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>nginx+factcgi 下使用 ob_flush</title>
		<link>http://www.lsproc.com/blog/use_ob_flush_on_nginx_fastcgi/</link>
		<comments>http://www.lsproc.com/blog/use_ob_flush_on_nginx_fastcgi/#comments</comments>
		<pubDate>Mon, 08 Mar 2010 03:45:23 +0000</pubDate>
		<dc:creator>lostsnow</dc:creator>
				<category><![CDATA[Linux&Webserver]]></category>
		<category><![CDATA[buffer]]></category>
		<category><![CDATA[fastcgi]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[ob_flush]]></category>
		<category><![CDATA[php]]></category>

		<guid isPermaLink="false">http://www.lsproc.com/blog/?p=376</guid>
		<description><![CDATA[转载时请标明文章原始出处和作者信息, 作者: lostsnow.http://www.lsproc.com/blog/use_ob_flush_on_nginx_fastcgi/
Nginx与php-cgi是两个独立的程序，通过TCP或Unix套接字通信，不像Apache那样是集成在一起的。所以，Nginx有fastcgi 缓冲区，数据超出缓冲区大小、或程序执行完，才会将内容输出到客户端。如果要使用ob_flush，不能开启gzip压缩输出。
nginx.conf:
fastcgi_buffer_size 4k;
fastcgi_buffers 8 4k;
gzip off;
php.ini:

output_buffering = Off


&#60;?php
set_time_limit(0);
ob_end_clean();
ob_implicit_flush(1);

for($i = 0; $i &#60; 10; $i++)
{
    echo $i . &#34;&#60;br /&#62;\n&#34;;
    echo str_repeat(&#039;&#039;, 1024*4);
    sleep(1);
}

其中 echo str_repeat('', 1024*4);
使得fastcgi_buffer_size 4k; 的缓冲区满，从而输出内容到浏览器
参考: http://blog.s135.com/nginx_php_v6/2/1/
-- EOF --
Related Posts2008-06-15 -- lighttpd + PHP(fastcgi) 配置 (0)2009-03-29 -- Nginx SSL 配置 (18)2008-10-23 -- [...]]]></description>
			<content:encoded><![CDATA[<p>转载时请标明文章原始出处和作者信息, 作者: <a href="http://www.lsproc.com/blog/">lostsnow</a>.<br /><a href="http://www.lsproc.com/blog/use_ob_flush_on_nginx_fastcgi/">http://www.lsproc.com/blog/use_ob_flush_on_nginx_fastcgi/</a></p>
<p>Nginx与php-cgi是两个独立的程序，通过TCP或Unix套接字通信，不像Apache那样是集成在一起的。所以，Nginx有fastcgi 缓冲区，数据超出缓冲区大小、或程序执行完，才会将内容输出到客户端。<strong>如果要使用ob_flush，不能开启gzip压缩输出。</strong></p>
<p>nginx.conf:</p>
<pre class="brush: text">fastcgi_buffer_size 4k;
fastcgi_buffers 8 4k;
gzip off;</pre>
<p>php.ini:</p>
<pre class="brush: text">
output_buffering = Off
</pre>
<pre class="brush: php">
&lt;?php
set_time_limit(0);
ob_end_clean();
ob_implicit_flush(1);

for($i = 0; $i &lt; 10; $i++)
{
    echo $i . &quot;&lt;br /&gt;\n&quot;;
    echo str_repeat(&#039;&#039;, 1024*4);
    sleep(1);
}
</pre>
<p>其中 echo str_repeat('', 1024*4);<br />
使得fastcgi_buffer_size 4k; 的缓冲区满，从而输出内容到浏览器</p>
<p>参考: http://blog.s135.com/nginx_php_v6/2/1/
<p>-- EOF --</p>
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>2008-06-15 -- <a href="http://www.lsproc.com/blog/lighttpd_phpfastcgi_config/" title="lighttpd + PHP(fastcgi) 配置">lighttpd + PHP(fastcgi) 配置</a> (0)</li><li>2009-03-29 -- <a href="http://www.lsproc.com/blog/nginx_ssl_config/" title="Nginx SSL 配置">Nginx SSL 配置</a> (18)</li><li>2008-10-23 -- <a href="http://www.lsproc.com/blog/nginx_rewrite_param/" title="nginx rewrite 的一些参数  ">nginx rewrite 的一些参数  </a> (1)</li><li>2008-03-18 -- <a href="http://www.lsproc.com/blog/configure_lamp/" title="lamp 相关配置 [Debian]">lamp 相关配置 [Debian]</a> (2)</li><li>2008-01-17 -- <a href="http://www.lsproc.com/blog/use_dbprefix_in_zendframework/" title="ZendFramework 使用数据表前缀">ZendFramework 使用数据表前缀</a> (0)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.lsproc.com/blog/use_ob_flush_on_nginx_fastcgi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>python 抓取页面</title>
		<link>http://www.lsproc.com/blog/python_spider/</link>
		<comments>http://www.lsproc.com/blog/python_spider/#comments</comments>
		<pubDate>Mon, 01 Feb 2010 06:34:31 +0000</pubDate>
		<dc:creator>lostsnow</dc:creator>
				<category><![CDATA[Program&Database]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[spider]]></category>

		<guid isPermaLink="false">http://www.lsproc.com/blog/?p=363</guid>
		<description><![CDATA[转载时请标明文章原始出处和作者信息, 作者: lostsnow.http://www.lsproc.com/blog/python_spider/

#coding=utf-8

import sys
import urllib2
import gzip
import StringIO

# 页面url
url = &#34;http://china.toocle.com/company/show/pdetail--1000436--10532651.html&#34;
# 页面编码
page_encode = &#34;gbk&#34;

request = urllib2.Request(url)
request.add_header(&#34;Accept-encoding&#34;, &#34;gzip&#34;)
usock = urllib2.urlopen(request)
page = usock.read()
# 处理gzip过的页面
if usock.headers.get(&#039;content-encoding&#039;, None) == &#039;gzip&#039;:
    page = gzip.GzipFile(fileobj=StringIO.StringIO(page)).read()

# 转unicode(gbk/utf8)
if not isinstance(page, unicode):
    page = unicode(page, page_encode)

print(page)

-- EOF --
Related Posts2008-11-10 -- python图形处理库Python Imaging Library (PIL) (0)2008-11-05 -- Dreamhost 上编译python并安装django (7)]]></description>
			<content:encoded><![CDATA[<p>转载时请标明文章原始出处和作者信息, 作者: <a href="http://www.lsproc.com/blog/">lostsnow</a>.<br /><a href="http://www.lsproc.com/blog/python_spider/">http://www.lsproc.com/blog/python_spider/</a></p>
<pre class="brush: python">
#coding=utf-8

import sys
import urllib2
import gzip
import StringIO

# 页面url
url = &quot;http://china.toocle.com/company/show/pdetail--1000436--10532651.html&quot;
# 页面编码
page_encode = &quot;gbk&quot;

request = urllib2.Request(url)
request.add_header(&quot;Accept-encoding&quot;, &quot;gzip&quot;)
usock = urllib2.urlopen(request)
page = usock.read()
# 处理gzip过的页面
if usock.headers.get(&#039;content-encoding&#039;, None) == &#039;gzip&#039;:
    page = gzip.GzipFile(fileobj=StringIO.StringIO(page)).read()

# 转unicode(gbk/utf8)
if not isinstance(page, unicode):
    page = unicode(page, page_encode)

print(page)
</pre>
<p>-- EOF --</p>
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>2008-11-10 -- <a href="http://www.lsproc.com/blog/python_pil/" title="python图形处理库Python Imaging Library (PIL)">python图形处理库Python Imaging Library (PIL)</a> (0)</li><li>2008-11-05 -- <a href="http://www.lsproc.com/blog/configure_python_and_django_on_dreamhost/" title="Dreamhost 上编译python并安装django">Dreamhost 上编译python并安装django</a> (7)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.lsproc.com/blog/python_spider/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>firefox crashes again and again</title>
		<link>http://www.lsproc.com/blog/firefox_crashes_again_and_again/</link>
		<comments>http://www.lsproc.com/blog/firefox_crashes_again_and_again/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 02:49:21 +0000</pubDate>
		<dc:creator>lostsnow</dc:creator>
				<category><![CDATA[HoradricCube]]></category>
		<category><![CDATA[crash]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[yslow]]></category>

		<guid isPermaLink="false">http://www.lsproc.com/blog/?p=356</guid>
		<description><![CDATA[转载时请标明文章原始出处和作者信息, 作者: lostsnow.http://www.lsproc.com/blog/firefox_crashes_again_and_again/
有图有真相

http://crash-stats.mozilla.com/report/index/4e66ca79-89a8-476c-a394-f824d2100125
yslow 是罪魁祸首
-- EOF --
Related Posts2007-07-16 -- Ubuntu 下安装 Tor (0)2006-03-06 -- 我用的Firefox扩展 (0)2006-03-01 -- Web设计札记 (1)]]></description>
			<content:encoded><![CDATA[<p>转载时请标明文章原始出处和作者信息, 作者: <a href="http://www.lsproc.com/blog/">lostsnow</a>.<br /><a href="http://www.lsproc.com/blog/firefox_crashes_again_and_again/">http://www.lsproc.com/blog/firefox_crashes_again_and_again/</a></p>
<p>有图有真相<br />
<a href="http://www.lsproc.com/blog/wp-content/uploads/2010/01/ff-crashes.jpg"><img src="http://www.lsproc.com/blog/wp-content/uploads/2010/01/ff-crashes.jpg" alt="" title="ff-crashes" width="538" height="366" class="alignnone size-full wp-image-357" /></a></p>
<p><a href="http://crash-stats.mozilla.com/report/index/4e66ca79-89a8-476c-a394-f824d2100125">http://crash-stats.mozilla.com/report/index/4e66ca79-89a8-476c-a394-f824d2100125</a><br />
yslow 是罪魁祸首
<p>-- EOF --</p>
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>2007-07-16 -- <a href="http://www.lsproc.com/blog/install_tor_under_ubuntu/" title="Ubuntu 下安装 Tor">Ubuntu 下安装 Tor</a> (0)</li><li>2006-03-06 -- <a href="http://www.lsproc.com/blog/my-firefox-extensions/" title="我用的Firefox扩展">我用的Firefox扩展</a> (0)</li><li>2006-03-01 -- <a href="http://www.lsproc.com/blog/web-design-tips/" title="Web设计札记">Web设计札记</a> (1)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.lsproc.com/blog/firefox_crashes_again_and_again/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>accessibility hosts</title>
		<link>http://www.lsproc.com/blog/accessibility_hosts/</link>
		<comments>http://www.lsproc.com/blog/accessibility_hosts/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 01:58:51 +0000</pubDate>
		<dc:creator>lostsnow</dc:creator>
				<category><![CDATA[HoradricCube]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[hosts]]></category>

		<guid isPermaLink="false">http://www.lsproc.com/blog/?p=350</guid>
		<description><![CDATA[转载时请标明文章原始出处和作者信息, 作者: lostsnow.http://www.lsproc.com/blog/accessibility_hosts/
#Search
74.125.39.99    www.google.com
74.125.39.103   www.google.com
74.125.39.104   www.google.com
74.125.39.105   www.l.google.com
#Images
74.125.39.99    images.google.com
74.125.39.103   images.google.com
74.125.39.104   images.google.com
74.125.39.105   images.google.com
74.125.39.106   images.google.com
74.125.39.147   images.google.com
74.125.77.99    tbn0.google.com
74.125.77.99    tbn1.google.com
74.125.77.103   tbn2.google.com
74.125.77.104   tbn3.google.com
74.125.77.105   tbn4.google.com
74.125.77.106   tbn5.google.com
74.125.77.147 [...]]]></description>
			<content:encoded><![CDATA[<p>转载时请标明文章原始出处和作者信息, 作者: <a href="http://www.lsproc.com/blog/">lostsnow</a>.<br /><a href="http://www.lsproc.com/blog/accessibility_hosts/">http://www.lsproc.com/blog/accessibility_hosts/</a></p>
<p>#Search<br />
74.125.39.99    www.google.com<br />
74.125.39.103   www.google.com<br />
74.125.39.104   www.google.com<br />
74.125.39.105   www.l.google.com</p>
<p>#Images<br />
74.125.39.99    images.google.com<br />
74.125.39.103   images.google.com<br />
74.125.39.104   images.google.com<br />
74.125.39.105   images.google.com<br />
74.125.39.106   images.google.com<br />
74.125.39.147   images.google.com<br />
74.125.77.99    tbn0.google.com<br />
74.125.77.99    tbn1.google.com<br />
74.125.77.103   tbn2.google.com<br />
74.125.77.104   tbn3.google.com<br />
74.125.77.105   tbn4.google.com<br />
74.125.77.106   tbn5.google.com<br />
74.125.77.147   tbn6.google.com</p>
<p>#Shopping<br />
74.125.39.99    base0.googlehosted.com<br />
74.125.39.103   base1.googlehosted.com<br />
74.125.39.104   base2.googlehosted.com<br />
74.125.39.105   base3.googlehosted.com<br />
74.125.39.106   base4.googlehosted.com<br />
74.125.39.147   base5.googlehosted.com</p>
<p>#Books<br />
74.125.39.100   books.google.com<br />
74.125.39.101   books.google.com<br />
74.125.39.102   books.google.com<br />
74.125.39.113   books.google.com<br />
74.125.39.138   books.google.com<br />
74.125.39.139   books.google.com<br />
74.125.39.100   bks0.books.google.com<br />
74.125.39.100   bks1.books.google.com<br />
74.125.39.101   bks2.books.google.com<br />
74.125.39.102   bks3.books.google.com<br />
74.125.39.113   bks4.books.google.com<br />
74.125.39.138   bks5.books.google.com<br />
74.125.39.139   bks6.books.google.com<br />
74.125.39.113   bks7.books.google.com<br />
74.125.39.138   bks8.books.google.com<br />
74.125.39.139   bks9.books.google.com</p>
<p>#Video<br />
74.125.39.100   video.google.com<br />
74.125.39.101   video.google.com<br />
74.125.39.102   video.google.com<br />
74.125.39.113   video.google.com<br />
74.125.39.138   video.google.com<br />
74.125.39.139   video.google.com<br />
74.125.39.100   0.gvt0.com<br />
74.125.39.101   1.gvt0.com<br />
74.125.39.102   2.gvt0.com<br />
74.125.39.113   3.gvt0.com<br />
74.125.39.138   4.gvt0.com<br />
74.125.39.139   5.gvt0.com</p>
<p>#Mail(POP3/SMTP)<br />
209.85.147.109  pop.gmail.com<br />
209.85.147.109  smtp.gmail.com</p>
<p>#WebMail<br />
64.233.189.18   mail.google.com<br />
64.233.189.19   mail.google.com<br />
64.233.189.83   mail.google.com<br />
64.233.189.18   www.gmail.com<br />
64.233.189.19   www.gmail.com<br />
64.233.189.83   www.gmail.com<br />
64.233.189.19   googlemail.l.google.com</p>
<p>#Docs<br />
64.233.189.101  writely-china.l.google.com<br />
64.233.189.101  writely.l.google.com<br />
64.233.189.102  docs.google.com<br />
64.233.189.101  docs.google.com<br />
64.233.189.100  docs.google.com</p>
<p>#Map<br />
64.233.189.104  map.google.com<br />
64.233.189.99   map.google.com<br />
64.233.189.147  map.google.com<br />
64.233.189.104  maps.google.com<br />
64.233.189.99   maps.google.com<br />
64.233.189.147  maps.google.com<br />
64.233.189.99   maps.gstatic.com<br />
203.208.39.93   khm.google.com<br />
203.208.39.91   mt0.google.com<br />
203.208.39.93   mt1.google.com<br />
203.208.39.91   mt2.google.com<br />
203.208.39.91   mt.l.google.com<br />
64.233.189.99   maps.l.google.com</p>
<p>#Scholar<br />
64.233.189.99   scholar.google.com<br />
64.233.189.104  scholar.google.com<br />
64.233.189.147  scholar.google.com<br />
64.233.189.104  scholar.l.google.com</p>
<p>#Group<br />
64.233.189.102  groups.google.com<br />
64.233.189.100  groups.google.com<br />
64.233.189.101  groups.google.com<br />
64.233.189.101  groups.l.google.com</p>
<p>#Picasa<br />
74.125.39.147   picasa.google.com<br />
74.125.39.91    photos.google.com<br />
74.125.39.91    picasaweb.google.com<br />
74.125.39.93    picasaweb.google.com<br />
74.125.39.136   picasaweb.google.com<br />
74.125.39.190   picasaweb.google.com<br />
74.125.39.91    lh0.ggpht.com<br />
74.125.39.93    lh1.ggpht.com<br />
74.125.39.136   lh2.ggpht.com<br />
74.125.39.190   lh3.ggpht.com<br />
74.125.39.91    lh4.ggpht.com<br />
74.125.39.93    lh5.ggpht.com<br />
74.125.39.136   lh6.ggpht.com<br />
74.125.39.190   lh7.ggpht.com<br />
203.208.39.104 picadaweb.google.com<br />
203.208.39.104 lh1.ggpht.com<br />
203.208.39.104 lh2.ggpht.com<br />
203.208.39.104 lh3.ggpht.com<br />
203.208.39.104 lh4.ggpht.com<br />
203.208.39.104 lh5.ggpht.com<br />
203.208.39.104 lh6.ggpht.com</p>
<p>#Translate<br />
74.125.39.100   translate.google.com<br />
74.125.39.101   translate.google.com<br />
74.125.39.102   translate.google.com<br />
74.125.39.113   translate.google.com<br />
74.125.39.138   translate.google.com<br />
74.125.39.139   translate.google.com</p>
<p>#Reader<br />
74.125.39.99    reader.google.com<br />
74.125.39.103   reader.google.com<br />
74.125.39.104   reader.google.com<br />
74.125.39.105   reader.google.com<br />
74.125.39.106   reader.google.com</p>
<p>#Sites<br />
64.233.161.9    sites.google.com<br />
74.125.53.9     sites.google.com<br />
74.125.39.102   sites.google.com<br />
74.125.39.139   sites.google.com<br />
74.125.45.9     sites.google.com<br />
74.125.39.139   sites.google.com</p>
<p>#Code<br />
74.125.53.9     code.google.com<br />
74.125.45.9     code.google.com<br />
64.233.161.9    code.google.com<br />
74.125.39.102   code.google.com<br />
209.85.137.9    code.google.com<br />
74.125.39.139   code.l.google.com</p>
<p>#Labs<br />
74.125.39.141   www.googlelabs.com<br />
74.125.39.141   appspot.l.google.com<br />
74.125.39.100   labs.google.com<br />
74.125.39.101   labs.google.com<br />
74.125.39.102   labs.google.com<br />
74.125.39.113   labs.google.com<br />
74.125.39.138   labs.google.com<br />
74.125.39.139   labs.google.com</p>
<p>#Knol<br />
74.125.39.100   knol.google.com<br />
74.125.39.101   knol.google.com<br />
74.125.39.102   knol.google.com<br />
74.125.39.113   knol.google.com<br />
74.125.39.138   knol.google.com<br />
74.125.39.139   knol.google.com</p>
<p>#Sketchup<br />
74.125.39.99    sketchup.google.com<br />
74.125.39.103   sketchup.google.com<br />
74.125.39.104   sketchup.google.com<br />
74.125.39.105   sketchup.google.com<br />
74.125.39.106   sketchup.google.com</p>
<p>#Pack<br />
74.125.39.99    pack.google.com<br />
74.125.39.103   pack.google.com<br />
74.125.39.104   pack.google.com<br />
74.125.39.105   pack.google.com<br />
74.125.39.106   pack.google.com</p>
<p>#News<br />
74.125.39.99    news.google.com<br />
74.125.39.103   news.google.com<br />
74.125.39.104   news.google.com<br />
74.125.39.105   news.google.com<br />
74.125.39.106   news.google.com<br />
74.125.39.147   news.google.com<br />
74.125.39.99    nt0.ggpht.com<br />
74.125.39.103   nt1.ggpht.com<br />
74.125.39.104   nt2.ggpht.com<br />
74.125.39.105   nt3.ggpht.com<br />
74.125.39.106   nt4.ggpht.com<br />
74.125.39.147   nt5.ggpht.com</p>
<p>#Calendar<br />
74.125.39.100   calendar.google.com<br />
74.125.39.101   calendar.google.com<br />
74.125.39.102   calendar.google.com<br />
74.125.39.113   calendar.google.com<br />
74.125.39.138   calendar.google.com<br />
74.125.39.139   calendar.google.com</p>
<p>#Blogger<br />
74.125.39.191   www.blogger.com<br />
74.125.39.191   blogger.l.google.com<br />
74.125.39.191   blogger.google.com</p>
<p>#Orkut<br />
74.125.47.85    www.orkut.com<br />
74.125.47.86    www.orkut.com<br />
74.125.47.85    orkut.google.com<br />
74.125.47.86    orkut.l.google.com</p>
<p>#Youtube<br />
74.125.39.100   www.youtube.com<br />
74.125.39.101   www.youtube.com<br />
74.125.39.102   www.youtube.com<br />
74.125.39.113   www.youtube.com</p>
<p>#Toolbar<br />
74.125.39.100   toolbar.google.com<br />
74.125.39.101   toolbar.google.com<br />
74.125.39.102   toolbar.google.com<br />
74.125.39.113   toolbar.google.com</p>
<p>#Apps<br />
74.125.39.99    apps.google.com<br />
74.125.39.103   apps.google.com<br />
74.125.39.104   apps.google.com<br />
74.125.39.115   apps.google.com</p>
<p>#Chrome<br />
74.125.39.99    chrome.google.com<br />
74.125.39.103   chrome.google.com<br />
74.125.39.104   chrome.google.com<br />
74.125.39.115   chrome.google.com</p>
<p>#Finance<br />
74.125.39.99    finance.google.com<br />
74.125.39.103   finance.google.com<br />
74.125.39.104   finance.google.com<br />
74.125.39.115   finance.google.com</p>
<p>#Desktop<br />
74.125.39.99    desktop.google.com<br />
74.125.39.103   desktop.google.com<br />
74.125.39.104   desktop.google.com<br />
74.125.39.115   desktop.google.com</p>
<p>#Ajax<br />
74.125.53.9     ajax.googleapis.com<br />
74.125.45.9     ajax.googleapis.com<br />
64.233.161.9    ajax.googleapis.com<br />
209.85.137.9    ajax.googleapis.com<br />
72.14.203.9     googleapis-ajax.l.google.com</p>
<p>#Modules<br />
74.125.39.132   1.ig.gmodules.com<br />
74.125.39.132   2.ig.gmodules.com<br />
74.125.39.132   3.ig.gmodules.com<br />
74.125.39.132   4.ig.gmodules.com<br />
74.125.39.132   5.ig.gmodules.com<br />
74.125.39.132   6.ig.gmodules.com</p>
<p>#Misc<br />
64.233.189.101  id.google.com<br />
64.233.189.102  id.google.com<br />
64.233.189.100  id.google.com<br />
64.233.189.100  id.l.google.com<br />
74.125.39.132   skins.gmodules.com<br />
74.125.39.132   googlehosted.l.google.com<br />
74.125.39.132   img0.gmodules.com<br />
74.125.39.99    blogsearch.google.com<br />
74.125.39.99    www2.l.google.com<br />
74.125.39.99    www.gstatic.com<br />
74.125.39.100   www3.l.google.com<br />
74.125.39.99    buttons.googlesyndication.com</p>
<p>#twitter<br />
<del datetime="2010-01-26T02:19:12+00:00">168.143.161.20 twitter.com<br />
168.143.161.20 www.twitter.com<br />
128.121.146.229 assets0.twitter.com<br />
128.121.146.229 assets1.twitter.com<br />
128.121.146.101 static.twitter.com<br />
128.121.146.229 assets2.twitter.com<br />
128.121.146.229 assets3.twitter.com<br />
65.74.185.41 twitter.zendesk.com<br />
65.74.185.41 help.twitter.com<br />
168.143.162.107 search.twitter.com</del></p>
<p>#facebook<br />
<del datetime="2010-01-26T02:19:12+00:00">124.40.42.105 www.facebook.com<br />
69.63.180.173 login.facebook.com<br />
69.192.34.110 s-static.ak.facebook.com<br />
69.63.176.69 secure-profile.facebook.com<br />
69.63.176.59 secure-media-sf2p.facebook.com<br />
69.63.178.13 ssl.facebook.com<br />
96.6.122.57 profile.ak.facebook.com<br />
64.211.21.152 b.static.ak.facebook.com<br />
</del></p>
<p>#wikipedia<br />
208.80.152.2 wikipedia.org<br />
208.80.152.2 www.wikipedia.org<br />
208.80.152.2 en.wikipedia.org<br />
208.80.152.2 zh.wikipedia.org</p>
<p>to be continued.......
<p>-- EOF --</p>
<h3  class="related_post_title">Random Posts</h3><ul class="related_post"><li>2007-11-30 -- <a href="http://www.lsproc.com/blog/anti_arp_on_linux/" title="linux防arp欺骗">linux防arp欺骗</a> (2)</li><li>2007-10-31 -- <a href="http://www.lsproc.com/blog/cakephp_conventions/" title="CakePHP 命名规则">CakePHP 命名规则</a> (1)</li><li>2007-07-27 -- <a href="http://www.lsproc.com/blog/php_mysql_study_3/" title="PHP 和 Mysql 学习笔记（三）">PHP 和 Mysql 学习笔记（三）</a> (0)</li><li>2008-01-13 -- <a href="http://www.lsproc.com/blog/add_coolcode_quicktag_for_wordpress/" title="为wordpress添加coolcode插件的quicktag">为wordpress添加coolcode插件的quicktag</a> (0)</li><li>2007-05-21 -- <a href="http://www.lsproc.com/blog/software_on_linux/" title="linux可以代替windows做的事情">linux可以代替windows做的事情</a> (0)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.lsproc.com/blog/accessibility_hosts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>bash if条件判断参数</title>
		<link>http://www.lsproc.com/blog/bash_if_parameters/</link>
		<comments>http://www.lsproc.com/blog/bash_if_parameters/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 06:10:44 +0000</pubDate>
		<dc:creator>lostsnow</dc:creator>
				<category><![CDATA[Linux&Webserver]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[shell]]></category>

		<guid isPermaLink="false">http://www.lsproc.com/blog/?p=348</guid>
		<description><![CDATA[转载时请标明文章原始出处和作者信息, 作者: lostsnow.http://www.lsproc.com/blog/bash_if_parameters/
[ -a FILE ] 如果 FILE 存在则为真。
[ -b FILE ] 如果 FILE 存在且是一个块特殊文件则为真。
[ -c FILE ] 如果 FILE 存在且是一个字特殊文件则为真。
[ -d FILE ] 如果 FILE 存在且是一个目录则为真。
[ -e FILE ] 如果 FILE 存在则为真。
[ -f FILE ] 如果 FILE 存在且是一个普通文件则为真。
[ -g FILE ] 如果 FILE 存在且已经设置了SGID则为真。
[ -h FILE ] 如果 FILE 存在且是一个符号连接则为真。
[ -k FILE ] 如果 [...]]]></description>
			<content:encoded><![CDATA[<p>转载时请标明文章原始出处和作者信息, 作者: <a href="http://www.lsproc.com/blog/">lostsnow</a>.<br /><a href="http://www.lsproc.com/blog/bash_if_parameters/">http://www.lsproc.com/blog/bash_if_parameters/</a></p>
<p>[ -a FILE ] 如果 FILE 存在则为真。</p>
<p>[ -b FILE ] 如果 FILE 存在且是一个块特殊文件则为真。</p>
<p>[ -c FILE ] 如果 FILE 存在且是一个字特殊文件则为真。</p>
<p>[ -d FILE ] 如果 FILE 存在且是一个目录则为真。</p>
<p>[ -e FILE ] 如果 FILE 存在则为真。</p>
<p>[ -f FILE ] 如果 FILE 存在且是一个普通文件则为真。</p>
<p>[ -g FILE ] 如果 FILE 存在且已经设置了SGID则为真。</p>
<p>[ -h FILE ] 如果 FILE 存在且是一个符号连接则为真。</p>
<p>[ -k FILE ] 如果 FILE 存在且已经设置了粘制位则为真。</p>
<p>[ -p FILE ] 如果 FILE 存在且是一个名字管道(F如果O)则为真。</p>
<p>[ -r FILE ] 如果 FILE 存在且是可读的则为真。</p>
<p>[ -s FILE ] 如果 FILE 存在且大小不为0则为真。</p>
<p>[ -t FD ] 如果文件描述符 FD 打开且指向一个终端则为真。</p>
<p>[ -u FILE ] 如果 FILE 存在且设置了SUID (set user ID)则为真。</p>
<p>[ -w FILE ] 如果 FILE 如果 FILE 存在且是可写的则为真。</p>
<p>[ -x FILE ] 如果 FILE 存在且是可执行的则为真。</p>
<p>[ -O FILE ] 如果 FILE 存在且属有效用户ID则为真。</p>
<p>[ -G FILE ] 如果 FILE 存在且属有效用户组则为真。</p>
<p>[ -L FILE ] 如果 FILE 存在且是一个符号连接则为真。</p>
<p>[ -N FILE ] 如果 FILE 存在 and has been mod如果ied since it was last read则为真。</p>
<p>[ -S FILE ] 如果 FILE 存在且是一个套接字则为真。</p>
<p>[ FILE1 -nt FILE2 ] 如果 FILE1 has been changed more recently than FILE2, or 如果 FILE1FILE2 does not则为真。</p>
<p>exists and [ FILE1 -ot FILE2 ] 如果 FILE1 比 FILE2 要老, 或者 FILE2 存在且 FILE1 不存在则为真。</p>
<p>[ FILE1 -ef FILE2 ] 如果 FILE1 和 FILE2 指向相同的设备和节点号则为真。</p>
<p>[ -o OPTIONNAME ] 如果 shell选项 “OPTIONNAME” 开启则为真。</p>
<p>[ -z STRING ] “STRING” 的长度为零则为真。</p>
<p>[ -n STRING ] or [ STRING ] “STRING” 的长度为非零 non-zero则为真。</p>
<p>[ STRING1 == STRING2 ] 如果2个字符串相同。 “=” may be used instead of “==” for strict POSIX compliance则为真。</p>
<p>[ STRING1 != STRING2 ] 如果字符串不相等则为真。</p>
<p>[ STRING1 < STRING2 ] 如果 “STRING1” sorts before “STRING2” lexicographically in the current locale则为真。</p>
<p>[ STRING1 > STRING2 ] 如果 “STRING1” sorts after “STRING2” lexicographically in the current locale则为真。</p>
<p><del datetime="2010-01-15T06:10:51+00:00">原文(已失效): http://hi.baidu.com/starlotus/blog/item/5707aeca34af14f753664f38.html </del>
<p>-- EOF --</p>
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>2010-01-09 -- <a href="http://www.lsproc.com/blog/linux_timeline/" title="linux timeline">linux timeline</a> (2)</li><li>2008-12-16 -- <a href="http://www.lsproc.com/blog/linux_webserver_cmd/" title="Webserver 维护常用命令">Webserver 维护常用命令</a> (9)</li><li>2008-11-10 -- <a href="http://www.lsproc.com/blog/useful_linux_command/" title="一些 linux 命令">一些 linux 命令</a> (0)</li><li>2008-08-31 -- <a href="http://www.lsproc.com/blog/install_network_card_driver_on_ubuntu/" title="ubuntu 安装Intel PRO100/1000系列网卡驱动">ubuntu 安装Intel PRO100/1000系列网卡驱动</a> (0)</li><li>2008-03-18 -- <a href="http://www.lsproc.com/blog/configure_lamp/" title="lamp 相关配置 [Debian]">lamp 相关配置 [Debian]</a> (2)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.lsproc.com/blog/bash_if_parameters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>cacti 图片中文乱码问题</title>
		<link>http://www.lsproc.com/blog/cacti_graph_with_chinese/</link>
		<comments>http://www.lsproc.com/blog/cacti_graph_with_chinese/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 09:02:56 +0000</pubDate>
		<dc:creator>lostsnow</dc:creator>
				<category><![CDATA[Linux&Webserver]]></category>
		<category><![CDATA[cacti]]></category>
		<category><![CDATA[乱码]]></category>

		<guid isPermaLink="false">http://www.lsproc.com/blog/?p=343</guid>
		<description><![CDATA[转载时请标明文章原始出处和作者信息, 作者: lostsnow.http://www.lsproc.com/blog/cacti_graph_with_chinese/
首先你需要一个中文字体
如simsun 等
将它放进 /usr/share/fonts目录中
然后执行下面的命令刷新字体缓存
fc-cache -f -v
然后再cacti 中设置 默认字体的路径为你使用的中文字体的路径
测试发现, 字体只能放到系统字体路径当中, 并要刷新字体缓存

-- EOF --
Related Posts2008-03-05 -- 解决webalizer 汉化后图表中乱码的问题 (0)2006-12-27 -- 再谈Wordpress的MySQL乱码问题解决方法 (3)2006-02-26 -- 一切又重新开始了 (0)]]></description>
			<content:encoded><![CDATA[<p>转载时请标明文章原始出处和作者信息, 作者: <a href="http://www.lsproc.com/blog/">lostsnow</a>.<br /><a href="http://www.lsproc.com/blog/cacti_graph_with_chinese/">http://www.lsproc.com/blog/cacti_graph_with_chinese/</a></p>
<p>首先你需要一个中文字体<br />
如simsun 等<br />
将它放进 /usr/share/fonts目录中</p>
<p>然后执行下面的命令刷新字体缓存</p>
<pre class="brush: shell">fc-cache -f -v</pre>
<p>然后再cacti 中设置 默认字体的路径为你使用的中文字体的路径</p>
<p>测试发现, 字体只能放到系统字体路径当中, 并要刷新字体缓存</p>
<p><a href="http://www.lsproc.com/blog/wp-content/uploads/2010/01/localhost_memory.png"><img src="http://www.lsproc.com/blog/wp-content/uploads/2010/01/localhost_memory-600x227.png" alt="" title="localhost_memory" width="600" height="227" class="alignnone size-medium wp-image-346" /></a>
<p>-- EOF --</p>
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>2008-03-05 -- <a href="http://www.lsproc.com/blog/webalizer_graphs_bad_encode/" title="解决webalizer 汉化后图表中乱码的问题">解决webalizer 汉化后图表中乱码的问题</a> (0)</li><li>2006-12-27 -- <a href="http://www.lsproc.com/blog/mysql_encode_error_in_wordpress/" title="再谈Wordpress的MySQL乱码问题解决方法">再谈Wordpress的MySQL乱码问题解决方法</a> (3)</li><li>2006-02-26 -- <a href="http://www.lsproc.com/blog/all-restart/" title="一切又重新开始了">一切又重新开始了</a> (0)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.lsproc.com/blog/cacti_graph_with_chinese/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>linux timeline</title>
		<link>http://www.lsproc.com/blog/linux_timeline/</link>
		<comments>http://www.lsproc.com/blog/linux_timeline/#comments</comments>
		<pubDate>Sat, 09 Jan 2010 05:45:42 +0000</pubDate>
		<dc:creator>lostsnow</dc:creator>
				<category><![CDATA[Linux&Webserver]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[timeline]]></category>

		<guid isPermaLink="false">http://www.lsproc.com/blog/?p=335</guid>
		<description><![CDATA[转载时请标明文章原始出处和作者信息, 作者: lostsnow.http://www.lsproc.com/blog/linux_timeline/
-- EOF --
Related Posts2010-01-15 -- bash if条件判断参数 (0)2008-12-16 -- Webserver 维护常用命令 (9)2008-11-10 -- 一些 linux 命令 (0)2008-08-31 -- ubuntu 安装Intel PRO100/1000系列网卡驱动 (0)2008-03-18 -- lamp 相关配置 [Debian] (2)]]></description>
			<content:encoded><![CDATA[<p>转载时请标明文章原始出处和作者信息, 作者: <a href="http://www.lsproc.com/blog/">lostsnow</a>.<br /><a href="http://www.lsproc.com/blog/linux_timeline/">http://www.lsproc.com/blog/linux_timeline/</a></p>
<p><div id="attachment_341" class="wp-caption alignnone" style="width: 488px"><a href="http://www.lsproc.com/blog/wp-content/uploads/2010/01/linux-timeline1.png"><img src="http://www.lsproc.com/blog/wp-content/uploads/2010/01/linux-timeline1-478x800.png" alt="linux timeline" title="linux-timeline" width="478" height="800" class="size-medium wp-image-341" /></a><p class="wp-caption-text">linux timeline</p></div>
<p>-- EOF --</p>
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>2010-01-15 -- <a href="http://www.lsproc.com/blog/bash_if_parameters/" title="bash if条件判断参数">bash if条件判断参数</a> (0)</li><li>2008-12-16 -- <a href="http://www.lsproc.com/blog/linux_webserver_cmd/" title="Webserver 维护常用命令">Webserver 维护常用命令</a> (9)</li><li>2008-11-10 -- <a href="http://www.lsproc.com/blog/useful_linux_command/" title="一些 linux 命令">一些 linux 命令</a> (0)</li><li>2008-08-31 -- <a href="http://www.lsproc.com/blog/install_network_card_driver_on_ubuntu/" title="ubuntu 安装Intel PRO100/1000系列网卡驱动">ubuntu 安装Intel PRO100/1000系列网卡驱动</a> (0)</li><li>2008-03-18 -- <a href="http://www.lsproc.com/blog/configure_lamp/" title="lamp 相关配置 [Debian]">lamp 相关配置 [Debian]</a> (2)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.lsproc.com/blog/linux_timeline/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>让subversion自动添加Id,Revision等keywords</title>
		<link>http://www.lsproc.com/blog/add_auto_props_in_subversion/</link>
		<comments>http://www.lsproc.com/blog/add_auto_props_in_subversion/#comments</comments>
		<pubDate>Mon, 26 Oct 2009 02:17:42 +0000</pubDate>
		<dc:creator>lostsnow</dc:creator>
				<category><![CDATA[Linux&Webserver]]></category>
		<category><![CDATA[subversion]]></category>
		<category><![CDATA[svn]]></category>

		<guid isPermaLink="false">http://www.lostk.com/blog/?p=306</guid>
		<description><![CDATA[转载时请标明文章原始出处和作者信息, 作者: lostsnow.http://www.lsproc.com/blog/add_auto_props_in_subversion/
linux下:
vim ~/.subversion/config
windows下
%APPDATA%\Subversion\config
编辑此文件
[auto-props]
*.html = svn:keywords=Id Reversion Date Author
*.php = svn:keywords=Id Reversion Date Author
*.css = svn:keywords=Id Reversion Date Author
*.js = svn:keywords=Id Reversion Date Author

并启用auto-props
[miscellany]
enable-auto-props = yes
这样在 svn add 和 svn import 时就会自动添加keywords
现有的源代码还是没有这个属性，我们得批量的设置一下，一行命令就搞定了（比如我们的目标是当前目录下的所有python源代码文件）：
find ./ -type f -name &#34;*.py&#34; &#124; xargs svn propset svn:keywords &#34;Id Reversion Date Author&#34;
-- EOF --
Related Posts2008-12-12 -- svn版本库重建/回滚 (1)]]></description>
			<content:encoded><![CDATA[<p>转载时请标明文章原始出处和作者信息, 作者: <a href="http://www.lsproc.com/blog/">lostsnow</a>.<br /><a href="http://www.lsproc.com/blog/add_auto_props_in_subversion/">http://www.lsproc.com/blog/add_auto_props_in_subversion/</a></p>
<p>linux下:</p>
<pre class="brush: text">vim ~/.subversion/config</pre>
<p>windows下</p>
<pre class="brush: text">%APPDATA%\Subversion\config</pre>
<p>编辑此文件</p>
<pre class="brush: text">[auto-props]
*.html = svn:keywords=Id Reversion Date Author
*.php = svn:keywords=Id Reversion Date Author
*.css = svn:keywords=Id Reversion Date Author
*.js = svn:keywords=Id Reversion Date Author
</pre>
<p>并启用auto-props</p>
<pre class="brush: text">[miscellany]
enable-auto-props = yes</pre>
<p>这样在 svn add 和 svn import 时就会自动添加keywords</p>
<p>现有的源代码还是没有这个属性，我们得批量的设置一下，一行命令就搞定了（比如我们的目标是当前目录下的所有python源代码文件）：</p>
<pre class="brush: shell">find ./ -type f -name &quot;*.py&quot; | xargs svn propset svn:keywords &quot;Id Reversion Date Author&quot;</pre>
<p>-- EOF --</p>
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>2008-12-12 -- <a href="http://www.lsproc.com/blog/svn_rollback/" title="svn版本库重建/回滚">svn版本库重建/回滚</a> (1)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.lsproc.com/blog/add_auto_props_in_subversion/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>It&#039;s time to change</title>
		<link>http://www.lsproc.com/blog/its_time_to_change/</link>
		<comments>http://www.lsproc.com/blog/its_time_to_change/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 04:19:23 +0000</pubDate>
		<dc:creator>lostsnow</dc:creator>
				<category><![CDATA[HoradricCube]]></category>

		<guid isPermaLink="false">http://www.lostk.com/blog/?p=294</guid>
		<description><![CDATA[转载时请标明文章原始出处和作者信息, 作者: lostsnow.http://www.lsproc.com/blog/its_time_to_change/

-- EOF --
Random Posts2010-01-09 -- linux timeline (2)2009-01-08 -- Ajax 提交数据加号与连接符丢失 (0)2008-11-10 -- python图形处理库Python Imaging Library (PIL) (0)2007-11-30 -- linux防arp欺骗 (2)2007-05-14 -- SciTE 实用设置 (0)]]></description>
			<content:encoded><![CDATA[<p>转载时请标明文章原始出处和作者信息, 作者: <a href="http://www.lsproc.com/blog/">lostsnow</a>.<br /><a href="http://www.lsproc.com/blog/its_time_to_change/">http://www.lsproc.com/blog/its_time_to_change/</a></p>
<p><a href="http://www.lsproc.com/blog/wp-content/uploads/2009/04/away.jpg"><img src="http://www.lsproc.com/blog/wp-content/uploads/2009/04/away-300x400.jpg" alt="away" title="away" width="300" height="400" class="alignnone size-thumbnail wp-image-295" /></a>
<p>-- EOF --</p>
<h3  class="related_post_title">Random Posts</h3><ul class="related_post"><li>2006-07-10 -- <a href="http://www.lsproc.com/blog/dos-hack-cmd/" title="DOS入侵命令全集">DOS入侵命令全集</a> (0)</li><li>2007-08-01 -- <a href="http://www.lsproc.com/blog/centos_50_yum/" title="CentOS 5.0 源">CentOS 5.0 源</a> (0)</li><li>2007-03-03 -- <a href="http://www.lsproc.com/blog/use-internet/" title="看看世界各地的哪些人可以用互联网[转]">看看世界各地的哪些人可以用互联网[转]</a> (0)</li><li>2009-01-08 -- <a href="http://www.lsproc.com/blog/ajax_char_lose/" title="Ajax 提交数据加号与连接符丢失">Ajax 提交数据加号与连接符丢失</a> (0)</li><li>2006-08-22 -- <a href="http://www.lsproc.com/blog/trouble-with-rebuild-system/" title="重装系统是件麻烦的事">重装系统是件麻烦的事</a> (0)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.lsproc.com/blog/its_time_to_change/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Nginx SSL 配置</title>
		<link>http://www.lsproc.com/blog/nginx_ssl_config/</link>
		<comments>http://www.lsproc.com/blog/nginx_ssl_config/#comments</comments>
		<pubDate>Sun, 29 Mar 2009 13:19:50 +0000</pubDate>
		<dc:creator>lostsnow</dc:creator>
				<category><![CDATA[Linux&Webserver]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[ssl]]></category>

		<guid isPermaLink="false">http://www.lostk.com/blog/?p=288</guid>
		<description><![CDATA[转载时请标明文章原始出处和作者信息, 作者: lostsnow.http://www.lsproc.com/blog/nginx_ssl_config/
使用OpenSSL生成证书
1、生成RSA密钥的方法
openssl genrsa -des3 -out privkey.pem 2048
这个命令会生成一个2048位的密钥，同时有一个des3方法加密的密码，如果你不想要每次都输入密码，可以改成：
openssl genrsa -out privkey.pem 2048
建议用2048位密钥，少于此可能会不安全或很快将不安全。
2、生成一个证书请求
openssl req -new -key privkey.pem -out cert.csr
这个命令将会生成一个证书请求，当然，用到了前面生成的密钥privkey.pem文件
这里将生成一个新的文件cert.csr，即一个证书请求文件，你可以拿着这个文件去数字证书颁发机构（即CA）申请一个数字证书。CA会给你一个新的文件cacert.pem，那才是你的数字证书。
如果是自己做测试，那么证书的申请机构和颁发机构都是自己。就可以用下面这个命令来生成证书：
openssl req -new -x509 -key privkey.pem -out cacert.pem -days 1095
这个命令将用上面生成的密钥privkey.pem生成一个数字证书cacert.pem
配置nginx

server
{
    listen       443;
    ssl on;
    ssl_certificate  /var/www/sslkey/cacert.pem;
    ssl_certificate_key /var/www/sslkey/privkey.pem;
  [...]]]></description>
			<content:encoded><![CDATA[<p>转载时请标明文章原始出处和作者信息, 作者: <a href="http://www.lsproc.com/blog/">lostsnow</a>.<br /><a href="http://www.lsproc.com/blog/nginx_ssl_config/">http://www.lsproc.com/blog/nginx_ssl_config/</a></p>
<p><strong>使用OpenSSL生成证书</strong></p>
<p>1、生成RSA密钥的方法</p>
<p>openssl genrsa -des3 -out privkey.pem 2048<br />
这个命令会生成一个2048位的密钥，同时有一个des3方法加密的密码，如果你不想要每次都输入密码，可以改成：<br />
openssl genrsa -out privkey.pem 2048<br />
建议用2048位密钥，少于此可能会不安全或很快将不安全。</p>
<p>2、生成一个证书请求<br />
openssl req -new -key privkey.pem -out cert.csr<br />
这个命令将会生成一个证书请求，当然，用到了前面生成的密钥privkey.pem文件<br />
这里将生成一个新的文件cert.csr，即一个证书请求文件，你可以拿着这个文件去数字证书颁发机构（即CA）申请一个数字证书。CA会给你一个新的文件cacert.pem，那才是你的数字证书。</p>
<p>如果是自己做测试，那么证书的申请机构和颁发机构都是自己。就可以用下面这个命令来生成证书：<br />
openssl req -new -x509 -key privkey.pem -out cacert.pem -days 1095<br />
这个命令将用上面生成的密钥privkey.pem生成一个数字证书cacert.pem</p>
<p><strong>配置nginx</strong></p>
<pre class="brush: text">
server
{
    listen       443;
    ssl on;
    ssl_certificate  /var/www/sslkey/cacert.pem;
    ssl_certificate_key /var/www/sslkey/privkey.pem;
    server_name  192.168.1.1;
    index index.html index.htm index.php;
    root  /var/www/test;

    .....
    ...
}
</pre>
<p>-- EOF --</p>
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>2010-03-08 -- <a href="http://www.lsproc.com/blog/use_ob_flush_on_nginx_fastcgi/" title="nginx+factcgi 下使用 ob_flush">nginx+factcgi 下使用 ob_flush</a> (0)</li><li>2008-10-23 -- <a href="http://www.lsproc.com/blog/nginx_rewrite_param/" title="nginx rewrite 的一些参数  ">nginx rewrite 的一些参数  </a> (1)</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.lsproc.com/blog/nginx_ssl_config/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
	</channel>
</rss>
