Neemem's Blog

eZ Publish 4.1 adds native support for Sun Solaris 10 and Oracle Database

neemem — Wed, 08 Oct 2008 10:18:32 +0800

On June 18th, 2008, during eZ Conference’s developer day, eZ Systems announced that the upcoming eZ Publish 4.1 will support Sun Solaris 10 and Oracle Database. In addition, new features that enhance the user experience were also presented, including a new version of the Online Editor and multi-upload functionality.

eZ’s focus with the eZ Publish Content Management System is to combine a powerful enterprise platform with a rich user interface.
“Our demanding customers, especially within the media industry, need a flexible and powerful platform capable of handling any type of content. They use eZ Publish to serve millions of visitors, and also for the easy-to-use interfaces that enable both editors and users to quickly publish their articles, blogs, videos, and more,” explains Bård Farstad, Co-Founder and Chief Technology Officer at eZ Systems.

Developer day took place at the new eZ Headquarters location in Skien, Norway. eZ developers from around the world came together to discuss and present on eZ Publish, eZ Components and the surrounding technologies. eZ Conference continues with two more days that include presentations about best practices for eZ’s products and eZ Publish for online digital media.

For more information on eZ Publish, visit http://ez.no/ezpublish
For more information on eZ Conference, visit http://conference.ez.no

Tags: ezpublish, headquarters location, native, oracle, solaris, sun solaris 10

nagios的安装和配置

neemem — Thu, 02 Oct 2008 16:51:54 +0800

什么是nagios？
nagios是一款网络管理软件，开源的软件。能够对网络内的主机和硬件设备进行状态监控。

nagios的优势：
免费；开源；高扩展性。

nagios能实现的功能：
1. 状态监控
2. 预警处理
3. 集中，规模化管理
4. 可视化显示方式

nagios的实现方式：nagios采用分布-集中的管理模式。在nagios服务器上安装nagios主程序，
在被监控主机上安装nagios代理程序。通过nagios主程序和nagios代理程序之间的通讯，监视
主机状态。
主程序和代理程序之间有两种工作方式，一种是主程序–>Active–>代理程序；另一种是
主程序–>passive–>代理程序；顾名思义，是以一方向另一方主动提出通讯需求来划分的。nagios的安装：
nagios服务器上需要安装以下包，nagios主程序，nagios的plugin程序，check_nrpe程序，imagepak包；
1、nagios安装
tar –xvzf nagios-2.0.tar.gz
mkdir /usr/local/nagios
pw useradd nagios –d /usr/local/nagios
pw addgroup root
chmod 755 /usr/local/nagios
cd nagios-2.0
./configure –prefix=/usr/local/nagios –with-gd-lib=/usr/local/lib –with-gd-inc=/usr/local/include
make all
make install
make install-init ##This installs the init script in /usr/local/etc/rc.d
make install-commandmode
make install-config ##将初始的配置文件安装到/usr/local/nagios/etc
注:在makeinstall-init这一步的时候可能会进行不下去，这时只要加个root组即可。
pw addgroup root
2、nagios-plugins的安装
tar –xvzf nagios-plugins-1.4.tar
mkdir /usr/local/nagios-plugins
cd nagios-plugins-1.4
./configure –prefix=/usr/local/nagios-plugins
make all
make install
mv /usr/local/nagios-plugins/libexec /usr/local/nagios
3、imagepak-base的安装
tar –xvzf imagepak-base.tar.gz
解压以后是base目录
cp –R base /usr/local/nagios/share/images/logos
4. nrpe的安装
安装nrpe(主要是使用check_nrpe模块)
#./configure –enable-ssl –enable-command-args
#make all
#cp src/check_nrpe /usr/local/nagios/libexec
vi checkcommands.cfg
定义check_nrpe命令
# ‘check_nrep’ command definition
define command{
command_name check_nrpe
command_line /usr/local/nagios/libexec/check_nrpe -H $HOSTADDRESS$ -c $ARG1$
}
restart nagios。

被监控主机需要安装nrpe和ncsa代理程序以及plugin程序。
1、安装nrpe与配置
#./configure –enable-ssl –enable-command-args
#make all
#mkdir -p /usr/local/nagios/etc
#mkdir /usr/local/nagios/bin
#mkdir /usr/local/nagios/libexec
#pw addgroup nagios
#pw useradd nagios -g nagios -d /usr/local/nagios/ -s /sbin/nologin
#chown -R nagios:nagios /usr/local/nagios
#cp nrpe.cfg /usr/local/nagios/etc
#cp src/nrpe /usr/local/nagios/bin
2、启动nrpe，端口为5666
/usr/local/nagios/bin/nrpe -c -n /etc/nrpe.cfg -d
3、安装监测的模块
nagios-plugins的安装
tar –xvzf nagios-plugins-1.4.tar
cd nagios-plugins-1.4
./configure –prefix=/usr/local/nagios
make all
make install

nagios的配置：
一、配置apache
在apache的配置文件httpd.conf中追加
ScriptAlias /nagios/cgi-bin/ /usr/local/nagios/sbin/
<Directory “/usr/local/nagios/sbin/”>
AllowOverride AuthConfig
Options ExecCGI
Order allow,deny
Allow from all
</Directory>
Alias /nagios/ /usr/local/nagios/share/
<Directory “/usr/local/nagios/share”>
Options None
AllowOverride AuthConfig
Order allow,deny
Allow from all
</Directory>
二、设置访问权限 1、在/usr/local/nagios/share目录下
vi .htaccess
AuthName “Nagios Access”
AuthType Basic
AuthUserFile /usr/local/nagios/etc/.htpasswd
require valid-user
2、在/usr/local/nagios/sbin目录下
vi .htpasswd
AuthName “Nagios Access”
AuthType Basic
AuthUserFile /usr/local/nagios/etc/.htpasswd
require valid-user
3、/usr/local/apache/bin/htpasswd –c /usr/local/nagios/etc/.htpasswd nagios
这个apache目录根据安装目录的不同而不同,主要所以用.htpasswd这个命令生成用户名和密码
三、配置nagios 1、在/usr/local/nagios/etc下是nagios的配置模板文件.cfg-sample,把.cfg-sample文件全部拷贝成.cfg
例如:cp nagios.cfg-sample nagios.cfg
全部拷贝完成即可.
2、vi dependencies.cfg (在2.0没有生成这个文件，自己创建)
然后保存即可.(在1.2用一个空的文件代替原来的dependencies.cfg文件,否则会出错)
3、修改minimal.cfg，把里面所有定义command的全部注释掉
vi /etc/minimal.cfg
修改cgi.cfg
修改use_authentication=1为use_authentication=0,即不用验证.不然有一些页面不会显示。
4、然后检查配置文件是否出错
/usr/local/nagios/bin/nagios –v /usr/local/nagios/etc/nagios.cfg
出现Total Warnings: 0
Total Errors: 0
为正常
出错的话,就是.cfg文件有问题
5、启动后台进程
/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
/usr/local/etc/rc.d/nagios start
6、http://yourip/nagios/index.html
(如果有些页面看不到的话.可以在cgi.cfg文件中
把带有authorized的选项前的#号去掉即可)
这些配置完以后，基本的nagios配置完成。

经验：nagios功能非常强大，但是配置也特别复杂。在部署nagios应用之前，一定要事先规划好；
哪些主机需要监视，都需要监视哪些服务，在监视中都采取哪些动作；而且要把他们条理
清楚的体现在cfg文件中，这样便于问题查找和扩充。

举几个cfg文件的例子。
hosts.cfg hostgroup.cfg service.cfg这三个配置文件对于简单的配置很重要，至于其他的配置文件，就要根据具体的应用来配置了。
Hosts.cfg
# ‘novell1′ host definition
define host{
use generic-host ; Name of host template to use
host_name 你想管理的机器名
alias 自己定义的别名
address 你想管理的机器的IP
check_command check-host-alive
max_check_attempts 10
notification_interval 120
notification_period 24×7
notification_options d,u,r
}
Hostgroup.cfg
# ‘novell-servers’ host group definition
define hostgroup{
hostgroup_name novell-servers
alias Novell Servers
contact_groups novell-admins
members 你想管理的机器名（可以用多个，中间用逗号分隔）
}
services.cfg
# Service definition
define service{
use generic-service ; Name of service template to use
host_name 你的机器名字
service_description SMTP
is_volatile 0
check_period 24×7
max_check_attempts 3
normal_check_interval 3
retry_check_interval 1
contact_groups novell-admins
notification_interval 120
notification_period 24×7
notification_options w,u,c,r
check_command check_smtp
}
contacts.cfg misccommands.cfg dependencies.cfg
nagios.cfg dependencies.cfg.bak resource.cfg
cgi.cfg escalations.cfg checkcommands.cfg
hostgroups.cfg services.cfg contactgroups.cfg
hosts.cfg timeperiods.cfg

以上三个配置文件对于想管理的机器，需要去配置，不过对于你的机器加入在不同的组里面所监视的服务是不同的，不同工作组的计算机在nagios的管理软件界面中的服务是不一样的，如果想要更多的监视一台服务器，那么就需要配置services.cfg文件，灵活的更改services.cfg文件对于使用好 nagios非常的重要。

Tags: images logos, nagios, nagios plugins, nrpe, 主程序, 配置

Apache vs Nginx : Web Server Performance Deathmatch

neemem — Thu, 02 Oct 2008 16:51:20 +0800

Deathmatch may be an overstatement but here are the results from some performance benchmarking.

The Setup:

Server:

CENTOS 5.1
Dual 2.4GHz Xeon CPUs
4GB RAM
RAID5 (4 x 15k disks)
Server and test client were connected via a consumer grade 10/100 switch

Configurations:

Basic static vhost
Keepalive turned on and with timeout of 15 seconds
GZIP turned on

I used autobench to perform the tests. Basically this is a perl script that sits on top of httperf and will run multiple tests in succession outputing the results to CSV. Awfully convenient.

All the tests were run against the same robots.txt file. Autobench ran the following command 20 times incrementing the request rate by 10 each time. I started at 10 requests per second and went up to 200.

httperf –timeout=5 –client=0/1 –server=HOST –port=80 –uri=/robots.txt –rate=X –send-buffer=4096 –recv-buffer=16384 –num-conns=5000 –num-calls=10

I performed two samples and arbitrarily used the second as the results shown here. At the bottom of this post I will have spreadsheet containing the data from these tests so you can check out all the results.

The Results:

Both web servers performed well in all the tests and had no issues completing the requests. So I will not mention the metrics that they finished very closely on, only the ones that they did not have similar results.

There were three httperf related tests that Nginx and Apache differed on more than small amount, reply rate, network I/O and response time.

This one really piqued my interest. It seems strange to me why we would see such a result from Apache. In both tests there was a big difference at the 700 request mark. Statistically the difference was only on the max reply rate. The average and minimum are within a few tenths of a percent consistent through the tests. The max for Apache in the first test was 734.7 and in the second 758.7, standard deviations of 13.9 and 22.9 respectively. I suppose the real question here is whether or not this is my test or how Apache acts. If it is the later it seems strange that dealing with 700 requests would be any different than dealing with 800. From 800 requests to 2000, the larger differences in these results seems more realistic, controlled and gradual.

The network I/O graph I find interesting mostly because I don’t know how to take it. On one hand it seems Apache is simply using more bandwidth to do the same number of requests as Nginx. Which would seem bad. On the other it could just mean that Apache does a better job of consuming and using the available pipe. Which would seem good. My hunch is that it is the former.

The response times are also interesting since Nginx responds consistently at 0.4 ms. I am not sure why this is since I don’t know the internals to Nginx but I imagine that it is something that is built into how it deals with requests.

While the httperf tests were running I collected sar data from that time. The results show that Nginx uses a good amount less CPU and produces equally less load.

Apache:

CPU:

Load:

Nginx:

CPU:

Load:

Thats all I got, pretty cool. Nginx seems to compete pretty well with Apache and there doesn’t seem like there is a good reason not to use it especially in CPU usage constrained situations (ie huge traffic, slow machines and etc).

Here’s my results spreadsheet for the detailed results of each httperf metric.

Tags: apache, nginx, overstatement, performance, performance benchmarking, setup server, standard deviations

lost iphone…..buy a windows mobile phone

neemem — Thu, 02 Oct 2008 16:50:39 +0800

buy wm-htc touch diamond……expensive

No tags for this post.

php 取得某个自然周的第一天和最后一天的方法

neemem — Fri, 26 Sep 2008 21:25:45 +0800

今天在写统计每周发帖情况的代码时，突然发觉在php语言里提供了那么多日期函数，但是真正要获得某个日期所在周的第一天和最后一天，还有点麻烦呢，上网搜索了一下，解决方案还真不多，不管怎么样，还是找了一个，稍微改装了一下，代码如下：

function getFirstDateOfWeek($dateStr){
$w = strftime(”%u”,strtotime($dateStr));
$sdate = strftime(”%Y-%m-%d”,strtotime($dateStr) - ($w-1)*86400) . ” 00:00:00″;

return $sdate;
}

function getLastDateOfWeek($dateStr){
$w= strftime(”%u”,strtotime($dateStr));
$edate = strftime(”%Y-%m-%d”,strtotime($date_time) + (7-$w)*86400) . ” 23:59:59″;

return $edate;
}

提供2个函数，通过传入指定日期，获取指定日期所在自然周的第一天和最后一天。

strftime函数对timestamp进行格式输出，其中%u - 星期几的十进制数表达 [1,7]，1 表示星期一，先通过strftime取得传入的指定日期在自然周中是第几天，然后再加上或减去一周中剩余的天数的总秒数即可。

No tags for this post.

Building an eZ publish module

neemem — Mon, 22 Sep 2008 11:55:58 +0800

The purpose of this rather short tutorial is to show users of eZ publish 3 willing to write some additional functions by exploiting the extensions functionality.

In the following article where ever we will mention an absolute path it will mean the path from the eZ publish root. We also suppose, that URL for our eZ publish site is http://www.example.com/path/index.php/mysite/

We will develop a simple extension for accessing EUR exchange rates. Of course, we need some source of exchange rates in an usable format. In our tutorial, we will use a service provided by European Central Bank. You can have a look at http://www.ecb.int/stats/eurofxref/eurofxref-xml.html to see actual exchange rates as HTML page. (This information is updated every working day at 2.15pm CE(S)T.) We are lucky because the bank provides this information also in the XML format at http://www.ecb.int/stats/eurofxref/eurofxref-daily.xml

Let’s have a brief look at this file:

<?xml version="1.0" encoding="UTF-8"?>

<gesmes:Envelope xmlns:gesmes="http://www.gesmes.org/xml/2002-08-01"

xmlns="http://www.ecb.int/vocabulary/2002-08-01/eurofxref">

<gesmes:subject>Reference rates</gesmes:subject>

<gesmes:Sender>

<gesmes:name>European Central Bank</gesmes:name>

</gesmes:Sender>

<Cube>

<Cube time='2004-04-15'>

<Cube currency='USD' rate='1.1912'/>

<Cube currency='JPY' rate='129.39'/>

<Cube currency='DKK' rate='7.4443'/>

...

<Cube currency='ZAR' rate='7.8591'/>

</Cube>

</Cube>

</gesmes:Envelope>

Perfect! We see that the most important information is stored in attributes of Cube tags: if the tag has the attribute named time, its value is the date, if it has the attribute named currency, its value is the currency symbol and the value of the attribute rate is the actual exchange rate. The format of the rate is suitable for us, so we do not need to do any post-processing.

In this tutorial we develop an extension named eurofxref which will contain one module with the same name. We want to have the possibility of including exchange rates to our templates and also we prepare an overview page like http://www.example.com/path/index.php/mysite/eurofxref/overview to see the entire table of exchange rates.

First, create the directory eurofxref under the /extension directory located in the root directory of eZ publish. If the /extension directory does not exist, then you have to create it. You must tell eZ publish that this extension exists by adding ActiveExtensions[]=eurofxref in the [ExtensionSettings] section of site.ini files. Preferably, you should do this by adding the following lines in /settings/override/site.ini.append.php. Please note that if you already have either [ExtensionSettings] or [RoleSettings] section in your site ini file, you have to add the line(s) to the corresponding section(s).

site.ini.append.php (partial content):

 

[ExtensionSettings]

ActiveExtensions[]=eurofxref

 

[RoleSettings]

PolicyOmitList[]=eurofxref

The last line ensures that an anonymous user will be not prompted for a login name and a password, when accessing information through the eurofxref module, for example by browsing http://www.example.com/path/index.php/mysite/eurofxref/overview. The eurofxref in the URL represents the module name, not the extension name. Every module can have an unlimited number of “views” - they represent different views of the data in the module. You can choose which view you want to see by entering its name after the name of the module (and the slash) in a URL.

Now create the directories design, modules and settings under /extension/eurofxref. Under design create the path /extension/eurofxref/design/standard/templates/eurofxref (by creating one subdirectory in this path at a time). In this directory we will put our template files, hence the directory name design. standard stands for the default design, templates is, as the name says, the directory used for storing templates and eurofxref is our “identifier”. From now on, we can use an eZ publish URI like design:eurofxref/name_of_template.tpl for accessing templates stored in this directory.

Under /extension/eurofxref/settings create the following two files:

design.ini.append.php (Exact content)

 

[ExtensionSettings]

DesignExtensions[]=eurofxref

and

module.ini.append.php (Exact content)

 

[ModuleSettings]

ExtensionRepositories[]=eurofxref

As you have probably found out, the purpose of design.ini.append.php is to allow using of templates located in our extension, in module.ini.append.php we say to eZ publish we are having modules in this extension.

Now we are coming to the most important part: creating the module eurofxref itself. Under /extension/eurofxref/modules create a directory eurofxref (the name of the module) and create the following files:

module.php (Exact content)

 

<?php

 

$Module = array( 'name' => 'Eurofxref' );

 

$ViewList = array();

$ViewList['overview'] = array(

   'script' => 'overview.php',

   'params' => array ( ) );

 

?>

overview.php (Exact content)

 

<?php

 

include_once( 'kernel/common/template.php' );

 

$tpl =& templateInit();

 

$Result = array();

$Result['content'] =& $tpl->fetch( 'design:eurofxref/overview.tpl' );

$Result['path'] = array( array( 'url' => false,

                               'text' => 'Euro Exchange Rates' ) );

?>

and

function_definition.php (Exact content)

 

<?php

 

$FunctionList = array();

 

$FunctionList['fxref'] = array(

'name' => 'fxref',

'call_method' => array( 

'include_file' => 'extension/eurofxref/modules/eurofxref/classes/eurofxref.php',

'class' => 'EuroFxRef',

'method' => 'fetchFX' ),

'parameter_type' => 'standard',

'parameters' => array() );

 

?>

The module.php file is used to connect the different views in the module, represented by keys in the $ViewList array (in our case ‘overview’) with the file names (overview.php). We can see that overview.php contains simple code to fetch and process the template file design:eurofxref/overview.tpl. We will create this file later.

If you have {let var_name=fetch( ‘module’, ‘function’, ‘parameters’ )} in the template, eZ publish will call a method whose parameters are defined in the file function_definition.php under the corresponding module. Having a look in our function_definition.php file, we see that if the template fetches the function fxref in our module (eurofxref), eZ publish will call the method EuroFxRef::fetchFX() which will be defined in /extension/eurofxref/modules/eurofxref/classes/eurofxref.php. In our simple example, we do not have any parameters in the fetch.

Create the directory classes under /extension/eurofxref/modules/eurofxref and place the following file in it:

eurofxref.php (Exact content)

 

<?php

 

include_once( 'lib/ezxml/classes/ezxml.php' );

 

class EuroFxRef

{

   // static

   function fetchFX()

   {

       $result = array( 'date' => false, 'fx' => array() );

 

       $fxXML = file_get_contents("http://www.ecb.int/stats/eurofxref/eurofxref-daily.xml");

 

       $xml = new eZXML();

       $dom =& $xml->domTree( $fxXML );

       $fxArray =& $dom->elementsByName( 'Cube' );

       foreach ( $fxArray as $fxRate )

       {

           if ( !$fxRate->hasAttributes() )

               continue;

           $currency = $fxRate->attributeValue( 'currency' );

           if ( $currency === false )

           {

               if ( $fxRate->attributeValue( 'time' ) != false )

               {

                   $datePieces = explode( '-', $fxRate->attributeValue( 'time' ) );

                   $result['date'] = mktime( 0, 0, 0, $datePieces[1], $datePieces[2], $datePieces[0] );

               }

           }

           else

           {

               $value = $fxRate->attributeValue( 'rate' );

               $result['fx'][$currency] = $value;

           }

       }

       return array( 'result' => $result );

   }

}

 

?>

Note that we are returning our data ($result) in an array element with the key ‘result’.

When the file is parsed and the result is returned, the $result array looks like:

$result = array( 'date' => 1081980000,

                    'fx' => array( 'USD' => 1.1912,

                                   'JPY' => 129.39,

                                   'DKK' => 7.4443,

                                   ...

                                   'ZAR' => 7.8591 ) )

The last file which we need to create before testing our new extension, is the template file overview.tpl under /extension/eurofxref/design/standard/templates/eurofxref. Put the following contents in it:

overview.tpl (Exact content)

 

<h1>Euro foreign exchange reference rates</h1>

 

{let rates=fetch( 'eurofxref', 'fxref' )}

Date: {$rates.date|l10n( 'date' )}<br />

<br />

 

<table border="1">

<tr><th> Currency </th><th> Value </th></tr>

{section loop=$rates.fx}

<tr><td> {$:key} </td><td> {$:item|l10n( 'number' )} </td></tr>

{/section}

</table>

{/let}

<br />

 

Source: <a href="http://www.ecb.int">European Central Bank</a>

As outlined before, we use let rates=fetch( ‘eurofxref’, ‘fxref’ ) to fetch data through the function EuroFxRef::fetchFX(). Using $rates.date we can output the date and we can cycle through elements of $rates.fx (with loop=$rates.fx).

If you point your browser to http://www.example.com/path/index.php/mysite/eurofxref/overview you should see a table with currency symbols and rates:

You can print the current exchange rate of your currency in any template just by including the following code in it.

(partial content)

 

{let rates=fetch( 'eurofxref', 'fxref' )}

1 EUR = {$rates.fx.USD|l10n( 'number' )} USD

{/let}

If you want to use this code on pages which are frequently used then you may consider some optimization. The problem is that the code will download the XML document every time the fetch function is called. One possible solution is to store the values into a database and if we know the data is valid next fetches will use these stored values instead of downloading the XML document from web again and again.

The second solution is much simpler but not so sophisticated. We can use the template function cache-block to cache a generated part of the page. Using this function is very simple:

(partial content)

 

{cache-block expiry=3600}

{let rates=fetch( 'eurofxref', 'fxref' )}

1 EUR = {$rates.fx.USD|l10n( 'number' )} USD

{/let}

{/cache-block}

We set the expiration period by setting the expiry parameter to the maximum number of seconds the element might be in the cache. In our example we use one hour (3600 seconds). We should put the entire content of overview.tpl into a cache block as well. Please note that this will cache something like “1 EUR = 1.1912 USD” rather than the information about rates. If you will use the code elsewhere it will download the XML document again.

If you want to create views that have parameters in an URL, (e.g. http://www.example.com/path/index.php/mysite/eurofxref/history/EUR, where history is the name of a view and EUR is a parameter), you have to add additional code to module.php, for example:

module.php (partial content)

 

$ViewList['history'] = array(

   'script' => 'history.php',

   'params' => array ( 'CurrencySymbol' ) );

You can retrieve the value of the parameters in your script with:

history.php (partial content)

 

<?php

   $currencySymbol = $Params['CurrencySymbol'];

A more complicated addition to our example is adding parameters to the fetch function called from a template. However this exceeds the scope of this article, we recommend to read the documentation and browse the eZ publish source code, for example have a look at /kernel/content/function_definition.php and see the source code of any function defined with the call_method key.

You can download the whole source code of the extension from this tutorial from http://ez.no/community/contributions/examples/euro_exchange_rates.

Tags: design, extension, ezpublish, module, templates

Neemem's Blog

eZ Publish 4.1 adds native support for Sun Solaris 10 and Oracle Database

Related posts

nagios的安装和配置

Related posts

Apache vs Nginx : Web Server Performance Deathmatch

Related posts

lost iphone…..buy a windows mobile phone

Related posts

php 取得某个自然周的第一天和最后一天的方法

Related posts

Building an eZ publish module

Related posts