1 Aug 2006 12:12
Re: Cherokee rpm files come alive
Manuel Arostegui Ramirez <manuel <at> todo-linux.com>
2006-08-01 10:12:08 GMT
2006-08-01 10:12:08 GMT
> El Lunes, 31 de Julio de 2006 12:54, Alvaro Lopez Ortega escribió: > > > > Yeah, I wrote a basic spec file for SuSE some time ago, but it has > > not received much attention since then: > > > > http://www.0x50.org/bugs/browser/cherokee/trunk/cherokee.spec.in > Hi all. After some hours working on the new cherokee.spec file i've decide not to rewrite it, not to reinvent the wheel. If you wonder why, it's easy to understand IMHO cherokee should be the same on every distribution, I mean, for example, by default RH-based system uses /var/www as DocumenRoot for Apache, but cherokee proyect don't wanna be Apache, do it? So, in my opinion is better for all cherokee users to have the same paths and the same files everywhere, in order to make cherokee independent from any system,i think that's the best way to make systems administrators feel good with cherokee in every system, Suse, Debian, Red Hat, OpenSolaris...they only will be worry about cherokee issues, not guessing where cherokee.conf is or where libplugin_nn.so is, cause it's will be the same in every linux/unix. Here is alo's spec file ---------------------------------- # Cherokee # Copyright (C) 2001-2006 Alvaro Lopez Ortega Name: cherokee Version: 0.5.4(Continue reading)
- lighttpd fails a 26.78% more than Cherokee.
+ Result: GOOD!
- Cherokee didn't crash one single time, lighttpd crashed
many times.
+ Result: Fair enough, a server should never ever crash.
- We have to review the performance with less than 200
simultaneous connections. I suppose we can improve the
performance in that case.
So, congratulations guys! We're on the right way.
I have read the Mail-Thread from May 2006 and would suggest to not
exclue the nginx because it's also a server which people use
RSS Feed