monline

(...) Modern Linux distro's, say Ubuntu (8.10) comes with a default PHP configuration of session.gc_probability = 0. This means that in general, session GC will never run(!). There is a unix cron job that runs every half hour and checks for old sessions to delete (see more at /etc/cron.d/php5) but this is done only if you're using the standard "files" as your session handler (check out the directive of session.save_handler on your machine to learn what php default sessions handler is but make sure to check that your application doesn't overwrite this), so for Drupal users using plain Debian/Ubuntu, stock LAMP packages and stock Drupal applications, this means that the PHP garbage collection, despite your best intentions, will also never run. (...)

The linked page describes it very well. Just a quick note for myself in case the original post disappears:

A good article, I used to set up FCGI the same way. I had to find all the necessary info myself, when I first tried to use FCGI with a multi-site setup (separate PHP config, etc. for each site), but I'm glad that meanwhile somebody took the time to write it down.

This blog post helped me a lot ... probably it'd have taken a few hours to figure out why mysql_connect() dies with a "No such file or directory" error. I had a feeling (while I was reading the readme in the Mac installer of the currently available MySQL server, which got obviously outdated years ago) that there're problems to be expected with the MySQL install.

A straight to the point guide on how to configure the built-in Apache (where are the config and command files), etc. As it turns out, it already ships with PHP support and it was already running for some reason. Never mind. The first thing I did after installing the OS was to set up a firewall (ipfw in this case), so having an Apache on the inside did really not matter much (probably took a few MBs of the memory). But now I need it anyway, so I'm not very upset that I didn't have to install it from scratch.

The key is the dh-make-php package. It contains the dh-make-pecl command, which can download and prepare PECL extensions so you can easily build a Debian package from them.

"This is a tale of two approaches to regular expression matching. One of them is in widespread use in the standard interpreters for many languages, including Perl. The other is used only in a few places, notably most implementations of awk and grep. The two approaches have wildly different performance characteristics ..."
A very interesting article on regular expression matching algorithms.

My experience shows that a lot of con emails come from Senegal. If you maintain a forum or some kind of social network website, you might want to consider to block users from Senegal IPs. Here's a PHP code snippet with the current IP ranges assgined to Senegal ISPs, etc.

Today I faced the problem of removing all occurances of a fixed number of characters from a string. I was curious how str_replace performed against preg_replace in this case.

Let's assume you want to mass-update a set of nodes or create a new revision for each of them. You could do this through the UI, but of course for hundreds (or thousands) of nodes this is not really an option. You can do this programatically with a small PHP script.