Tue, 01 Sep 2009 10:23:00 GMT慢慢有功劳http://blog.csdn.net/FeiSan/http://blog.csdn.net/FeiSan/archive/2009/09/01/4506061.aspxhttp://blog.csdn.net/FeiSan/comments/4506061.aspx0http://blog.csdn.net/FeiSan/comments/commentRss/4506061.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=4506061做网络编程的时候，经常需要把接收到的数据用16进制的方式打印出来，方便查看。今天发现在Python下有这样一个简单的方法。   >>> "hello".encode("hex") '68656c6c6f'   相应的还可以 >>> '68656c6c6f'.decode("hex") 'hello'   查了一下手册，还有这些codec可用 Codec Aliases Operand type Purpose base64_codec base64, base-64 byte string Convert operand to MIME base64 bz2_codec bz2 byte string Compress t<img src ="http://blog.csdn.net/FeiSan/aggbug/4506061.aspx" width = "1" height = "1" /><img src="http://www1.feedsky.com/t1/265562858/FeiSan/csdn.net/s.gif?r=http://blog.csdn.net/FeiSan/archive/2009/09/01/4506061.aspx" border="0" height="0" width="0" style="position:absolute" /><p class="fswww1"><a href="http://www1.feedsky.com/r/l/csdn.net/FeiSan/265562858/art01.html" target="_blank"><img border="0" ismap="ismap" src="http://www1.feedsky.com/r/i/csdn.net/FeiSan/265562858/art01.gif" onerror="this.style.display='none'" /></a></p>Tue, 01 Sep 2009 18:23:00 +0800肥三http://blog.csdn.net/FeiSan/archive/2009/09/01/4506061.aspx#Feedbackhttp://blog.csdn.net/FeiSan/archive/2009/09/01/4506061.aspx肥三http://blog.csdn.net/FeiSan/archive/2009/09/01/4506061.aspxhttp://blog.csdn.net/FeiSan/feed.aspxcsdn.net/FeiSan/~1073992/265562858/1073991http://blog.csdn.net/FeiSan/archive/2009/07/18/4359442.aspxhttp://blog.csdn.net/FeiSan/comments/4359442.aspx0http://blog.csdn.net/FeiSan/comments/commentRss/4359442.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=4359442http://code.google.com/p/unladen-swallow/wiki/Release2009Q2 <img src ="http://blog.csdn.net/FeiSan/aggbug/4359442.aspx" width = "1" height = "1" /><img src="http://www1.feedsky.com/t1/265562859/FeiSan/csdn.net/s.gif?r=http://blog.csdn.net/FeiSan/archive/2009/07/18/4359442.aspx" border="0" height="0" width="0" style="position:absolute" /><p class="fswww1"><a href="http://www1.feedsky.com/r/l/csdn.net/FeiSan/265562859/art01.html" target="_blank"><img border="0" ismap="ismap" src="http://www1.feedsky.com/r/i/csdn.net/FeiSan/265562859/art01.gif" onerror="this.style.display='none'" /></a></p>Sat, 18 Jul 2009 21:37:00 +0800肥三http://blog.csdn.net/FeiSan/archive/2009/07/18/4359442.aspx#Feedbackhttp://blog.csdn.net/FeiSan/archive/2009/07/18/4359442.aspx肥三http://blog.csdn.net/FeiSan/archive/2009/07/18/4359442.aspxhttp://blog.csdn.net/FeiSan/feed.aspxcsdn.net/FeiSan/~1073992/265562859/1073991http://blog.csdn.net/FeiSan/archive/2009/04/26/4127047.aspxhttp://blog.csdn.net/FeiSan/comments/4127047.aspx0http://blog.csdn.net/FeiSan/comments/commentRss/4127047.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=4127047<br />最近买了个上网本，今天又去办了个电信的3G无线宽带帐户。<br /><br />估计以后出门这些都是我的随身装备了。<br /><br />以前总是不敢出门，出门也不敢离家太远，现在能稍微好一点了。。。<br /><img src ="http://blog.csdn.net/FeiSan/aggbug/4127047.aspx" width = "1" height = "1" /><p class="fswww1"><a href="http://www1.feedsky.com/r/l/csdn.net/FeiSan/265562860/art01.html" target="_blank"><img border="0" ismap="ismap" src="http://www1.feedsky.com/r/i/csdn.net/FeiSan/265562860/art01.gif" onerror="this.style.display='none'" /></a></p>Mon, 27 Apr 2009 07:14:00 +0800肥三http://blog.csdn.net/FeiSan/archive/2009/04/26/4127047.aspx#Feedbackhttp://blog.csdn.net/FeiSan/archive/2009/04/26/4127047.aspx肥三http://blog.csdn.net/FeiSan/archive/2009/04/26/4127047.aspxhttp://blog.csdn.net/FeiSan/feed.aspxcsdn.net/FeiSan/~1073992/265562860/1073991http://blog.csdn.net/FeiSan/archive/2009/04/17/4087138.aspxhttp://blog.csdn.net/FeiSan/comments/4087138.aspx0http://blog.csdn.net/FeiSan/comments/commentRss/4087138.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=4087138<br />在网上看到的，记录一下<br /><br />http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/<br /><br />大致的方法是：<br />首先减小innodb_max_dirty_pages_pct参数值，让内存中的数据尽快写到磁盘上；<br />然后查看Innodb_buffer_pool_pages_dirty状态值，减少到一定程度的时候，就可以按正常方式关闭数据库了。<br /><br />具体请看原文。<br /><br /><br /><br /><img src ="http://blog.csdn.net/FeiSan/aggbug/4087138.aspx" width = "1" height = "1" /><p class="fswww1"><a href="http://www1.feedsky.com/r/l/csdn.net/FeiSan/265562861/art01.html" target="_blank"><img border="0" ismap="ismap" src="http://www1.feedsky.com/r/i/csdn.net/FeiSan/265562861/art01.gif" onerror="this.style.display='none'" /></a></p>Fri, 17 Apr 2009 22:14:00 +0800肥三http://blog.csdn.net/FeiSan/archive/2009/04/17/4087138.aspx#Feedbackhttp://blog.csdn.net/FeiSan/archive/2009/04/17/4087138.aspx肥三http://blog.csdn.net/FeiSan/archive/2009/04/17/4087138.aspxhttp://blog.csdn.net/FeiSan/feed.aspxcsdn.net/FeiSan/~1073992/265562861/1073991http://blog.csdn.net/FeiSan/archive/2008/12/11/3500288.aspxhttp://blog.csdn.net/FeiSan/comments/3500288.aspx0http://blog.csdn.net/FeiSan/comments/commentRss/3500288.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3500288<br />前两天在日志里提到了一个Linux内核的BUG。<br /><br />现在找到一个临时办法可以关闭这些信息<br />执行一下<br />echo "0" >/sys/devices/system/edac/mc/log_ue<br />echo "0" >/sys/devices/system/edac/mc/log_ce<br />那些报警信息就看不到了<br /><br />关于edac_mc模块，可以看看 http://buttersideup.com/edacwiki/FrontPage<br /><img src ="http://blog.csdn.net/FeiSan/aggbug/3500288.aspx" width = "1" height = "1" /><p class="fswww1"><a href="http://www1.feedsky.com/r/l/csdn.net/FeiSan/265562862/art01.html" target="_blank"><img border="0" ismap="ismap" src="http://www1.feedsky.com/r/i/csdn.net/FeiSan/265562862/art01.gif" onerror="this.style.display='none'" /></a></p>Fri, 12 Dec 2008 03:12:00 +0800肥三http://blog.csdn.net/FeiSan/archive/2008/12/11/3500288.aspx#Feedbackhttp://blog.csdn.net/FeiSan/archive/2008/12/11/3500288.aspx肥三http://blog.csdn.net/FeiSan/archive/2008/12/11/3500288.aspxhttp://blog.csdn.net/FeiSan/feed.aspxcsdn.net/FeiSan/~1073992/265562862/1073991http://blog.csdn.net/FeiSan/archive/2008/12/07/3468970.aspxhttp://blog.csdn.net/FeiSan/comments/3468970.aspx0http://blog.csdn.net/FeiSan/comments/commentRss/3468970.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3468970<br />最近在为BUG抓狂，MySQL的，nmdb的，当然更多还是自己的。<br /><br />nmdb的BUG是关于它的python binding的。一个同事发现，在一台机器上向nmdb写入一个值，在另一台机器上读不出。当时发现是32位系统的机器和64位系统的机器互相不能读取对方写的数据（当然是写到同一个nmdb里的）。于是给作者发邮件报告了这个BUG。通了几封邮件，附上一些测试文件，今天收到回信了：<br /><br />The bug is in the python code, when autopickling is enabled (the default), it's possible that it doesn't even work when running across different machines (even if they are all 32 or 64 bits).<br /><br />I'm about to leave, but to work around it you can disable the autopickling <img src ="http://blog.csdn.net/FeiSan/aggbug/3468970.aspx" width = "1" height = "1" /><p class="fswww1"><a href="http://www1.feedsky.com/r/l/csdn.net/FeiSan/265562863/art01.html" target="_blank"><img border="0" ismap="ismap" src="http://www1.feedsky.com/r/i/csdn.net/FeiSan/265562863/art01.gif" onerror="this.style.display='none'" /></a></p>Mon, 08 Dec 2008 04:33:00 +0800肥三http://blog.csdn.net/FeiSan/archive/2008/12/07/3468970.aspx#Feedbackhttp://blog.csdn.net/FeiSan/archive/2008/12/07/3468970.aspx肥三http://blog.csdn.net/FeiSan/archive/2008/12/07/3468970.aspxhttp://blog.csdn.net/FeiSan/feed.aspxcsdn.net/FeiSan/~1073992/265562863/1073991http://blog.csdn.net/FeiSan/archive/2008/12/02/3430599.aspxhttp://blog.csdn.net/FeiSan/comments/3430599.aspx1http://blog.csdn.net/FeiSan/comments/commentRss/3430599.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3430599<br />最近应用的数据量越来越大，访问量也越来越大，MySQL数据库不堪重负，考虑把部分数据用key-value类型的文件数据库存储。<br /><br />由于对速度要求比较高，所以一开始选用了据说很快的qdbm。测试了一下，的确很快，接口也非常简单。但是遇到两个问题，<br /><br />第一个是备份的问题。qdbm带了一些管理工具，其中也有exportdb/importdb这样的功能，但是对运行中的数据文件不能操作。暂时只能先copy一份，然后repair，感觉不是很好。<br /><br />第二个问题比较麻烦，在测试中，当数据文件超过2.1G以后，就写不进数据了。qdbm的作者在文档里说到：<br />As for many file systems, it is impossible to handle a file whose size is more than 2GB. To deal with this problem, QDBM provides a directory database containing multiple database file<img src ="http://blog.csdn.net/FeiSan/aggbug/3430599.aspx" width = "1" height = "1" /><p class="fswww1"><a href="http://www1.feedsky.com/r/l/csdn.net/FeiSan/265562864/art01.html" target="_blank"><img border="0" ismap="ismap" src="http://www1.feedsky.com/r/i/csdn.net/FeiSan/265562864/art01.gif" onerror="this.style.display='none'" /></a></p>Wed, 03 Dec 2008 01:22:00 +0800肥三http://blog.csdn.net/FeiSan/archive/2008/12/02/3430599.aspx#Feedbackhttp://blog.csdn.net/FeiSan/archive/2008/12/02/3430599.aspx肥三http://blog.csdn.net/FeiSan/archive/2008/12/02/3430599.aspxhttp://blog.csdn.net/FeiSan/feed.aspxcsdn.net/FeiSan/~1073992/265562864/1073991http://blog.csdn.net/FeiSan/archive/2008/11/23/3353672.aspxhttp://blog.csdn.net/FeiSan/comments/3353672.aspx1http://blog.csdn.net/FeiSan/comments/commentRss/3353672.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3353672最近遇到了几次MySQL服务崩溃重启。昨天就连续遇到两次。<img src ="http://blog.csdn.net/FeiSan/aggbug/3353672.aspx" width = "1" height = "1" /><p class="fswww1"><a href="http://www1.feedsky.com/r/l/csdn.net/FeiSan/265562865/art01.html" target="_blank"><img border="0" ismap="ismap" src="http://www1.feedsky.com/r/i/csdn.net/FeiSan/265562865/art01.gif" onerror="this.style.display='none'" /></a></p>Sun, 23 Nov 2008 17:56:00 +0800肥三http://blog.csdn.net/FeiSan/archive/2008/11/23/3353672.aspx#Feedbackhttp://blog.csdn.net/FeiSan/archive/2008/11/23/3353672.aspx肥三http://blog.csdn.net/FeiSan/archive/2008/11/23/3353672.aspxhttp://blog.csdn.net/FeiSan/feed.aspxcsdn.net/FeiSan/~1073992/265562865/1073991http://blog.csdn.net/FeiSan/archive/2008/11/13/3294084.aspxhttp://blog.csdn.net/FeiSan/comments/3294084.aspx3http://blog.csdn.net/FeiSan/comments/commentRss/3294084.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3294084<br />今天跑去机房把一台有问题的服务器重装了。<br /><br />回到家，检查一下所有的机器，结果发现一台服务器不停的打印错误信息：<br /><br />Message from syslogd@ at Thu Nov 13 21:51:21 2008 ...<br />www2 kernel: EDAC MC0: UE row 7, channel-a= 0 channel-b= 1 labels "-": (Branch=0 DRAM-Bank=2 RDWR=Read RAS=5074 CAS=0 FATAL Err=0x4)<br />Message from syslogd@ at Thu Nov 13 21:51:22 2008 ...<br />www2 kernel: EDAC MC0: UE row 0, channel-a= 0 channel-b= 1 labels "-": (Branch=0 DRAM-Bank=6 RDWR=Read RAS=4255 CAS=0 FATAL Err=0x4)<br />Message from syslogd@<img src ="http://blog.csdn.net/FeiSan/aggbug/3294084.aspx" width = "1" height = "1" /><p class="fswww1"><a href="http://www1.feedsky.com/r/l/csdn.net/FeiSan/265562866/art01.html" target="_blank"><img border="0" ismap="ismap" src="http://www1.feedsky.com/r/i/csdn.net/FeiSan/265562866/art01.gif" onerror="this.style.display='none'" /></a></p>Fri, 14 Nov 2008 05:55:00 +0800肥三http://blog.csdn.net/FeiSan/archive/2008/11/13/3294084.aspx#Feedbackhttp://blog.csdn.net/FeiSan/archive/2008/11/13/3294084.aspx肥三http://blog.csdn.net/FeiSan/archive/2008/11/13/3294084.aspxhttp://blog.csdn.net/FeiSan/feed.aspxcsdn.net/FeiSan/~1073992/265562866/1073991http://blog.csdn.net/FeiSan/archive/2008/11/12/3282545.aspxhttp://blog.csdn.net/FeiSan/comments/3282545.aspx0http://blog.csdn.net/FeiSan/comments/commentRss/3282545.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3282545Understanding security changes in Flash Player 10：http://www.adobe.com/devnet/flashplayer/articles/fplayer10_security_changes.htmlPolicy file changes in Flash Player 9 and Flash Player 10：http://www.adobe.com/devnet/flashplayer/articles/fplayer9_security.htmlcrossdomain.xml里增加新内容了。。。那些做slideshow的，要注意了！<img src ="http://blog.csdn.net/FeiSan/aggbug/3282545.aspx" width = "1" height = "1" /><p class="fswww1"><a href="http://www1.feedsky.com/r/l/csdn.net/FeiSan/265562867/art01.html" target="_blank"><img border="0" ismap="ismap" src="http://www1.feedsky.com/r/i/csdn.net/FeiSan/265562867/art01.gif" onerror="this.style.display='none'" /></a></p>Thu, 13 Nov 2008 00:13:00 +0800肥三http://blog.csdn.net/FeiSan/archive/2008/11/12/3282545.aspx#Feedbackhttp://blog.csdn.net/FeiSan/archive/2008/11/12/3282545.aspx肥三http://blog.csdn.net/FeiSan/archive/2008/11/12/3282545.aspxhttp://blog.csdn.net/FeiSan/feed.aspxcsdn.net/FeiSan/~1073992/265562867/1073991