Re: Runaway pyblosxom processes

Wari Wahab <[email protected]>
Newsgroups gmane.comp.web.pyblosxom.user,gmane.comp.web.pyblosxom.devel
Message-ID <1078472637.8402.26.camel@minisync>
On Thu, 2004-03-04 at 16:56, Robert Wall wrote:
> From what I can see in my logs there is no specific requests 
> that consistently cause trouble.  It may be worth noting that there are 
> now 1700+ posts in my "blog" (it's not really a blog) directory!
      ^^^^^^^^^^^

This could possibly be the reason why. When two or more requests comes
in, pyblosxom might be busy reading files, and stat'ing them. On a busy
server, querying a huge directory recursively with 'ls' could also use
up the CPU to the max.

You could try partitioning your categories, but that would break the
site flow. BTW, see if removing some plugins helps pyblosxom and the
server, especially plugins that traverses through your blog tree, like
the calendar, archives, and the month display. It may help if you have a
seperate flavour that renders those on cron and output to text, and use
Will's include plugin, so they won't be a burden anymore.

I've not run pyblosxom on any of the *BSDs yet, so I don't know if this
problem is a known issue. But, I believe that *BSDs are more stable, and
should not produce the kind of behaviour that you talked about.
Especially the fact that slowlaris is doing the job better. It could be
python, and how it's compiled on the server. Python 2.3 /may/ help, but
your mileage may vary.



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.