Adam Culp, well-known PHP community member and organizer of both the Sunshine PHP conference and ZendCon, has started up a new podcast that's targeted at blending the two things he enjoys most - geeky "stuff" and running.

My plans behind the podcast is to bring together two things I love to do…programming, and running. It only makes sense that I would want to share in both areas, and a podcast is a great way to do that. With the resurgence of podcasts lately I felt a little bit of peer pressure to attempt my own, and so far I have received wonderful reviews from PHP developers who also run, or runners who are also programmers.

You can find out more about the show over on rungeekradio.com or just tune in to the first episode and see what you think. This first show deals with conferences, user group talks and performance audit tools. If you enjoy the show, be sure to subscribe to the feed to get more episodes as they're released.

On the ReviewSignal blog today there's a post looking at their use of long running PHP processes and how they got around some of the common problems.

Here at Review Signal, I use a lot of PHP code and one of the challenges is getting PHP to run for long periods of time. Here are two sample problems that I deal with at Review Signal that require PHP processes to run for long periods of time or indefinitely: data processing and Twitter streaming API data.

They talk some about their use of the PHP CLI, bash and cron to execute their scripts. There's a bit about the difference between executing a script in ssh versus cron and how to use "nohup" to have it execute in the background. They show how to set up a cron job and, more specifically, how their script pulls from the Twitter API via a bash script to check if it's already running.

On the blog of the Agave Group today, there's this new post showing how to correct an issue that a PHP/MySQL install has with the OS X version 10.4.

I recently upgraded my mac to OS 10.4. Overall I've been pleased. Recently I decided to fire up PHP and mySQL and ran into some trouble.

Everything was moving along nicely - until I tried to connect to my database from a PHP page. To make a (really) long story short, a bunch of research revealed that since OS 10.4, the PHP install tries to connect to mySQL via the socket: /var/mysql/mysql.sock, but mySQL uses /tmp/mysql.sock. So they won't talk to one another. The trick is to change your php.ini to point to /tmp/mysql.sock.

Included is also a mini-guide to getting PHP working on OS X, and how he solved his problem (where to find the php.ini and change the value it needed).

On the blog of the Agave Group today, there's this new post showing how to correct an issue that a PHP/MySQL install has with the OS X version 10.4.

I recently upgraded my mac to OS 10.4. Overall I've been pleased. Recently I decided to fire up PHP and mySQL and ran into some trouble.

Everything was moving along nicely - until I tried to connect to my database from a PHP page. To make a (really) long story short, a bunch of research revealed that since OS 10.4, the PHP install tries to connect to mySQL via the socket: /var/mysql/mysql.sock, but mySQL uses /tmp/mysql.sock. So they won't talk to one another. The trick is to change your php.ini to point to /tmp/mysql.sock.

Included is also a mini-guide to getting PHP working on OS X, and how he solved his problem (where to find the php.ini and change the value it needed).