Tuesday, December 20, 2005

PHP on Apache and Pear not using same version of PHP

There are so many ways you get this error, usually masked as something else.

What happens is, you compile and install a new version of PHP. It installs for you the mod_php or libphp4.so file so that apache can use it... and as long as you have a php.ini, it does. A problem scenario might be when you attempt to use Pear to install something, in my case Image_Color, and it says it 'gd' is not enabled in PHP -- despite that I just enabled it, and my phpinfo says it's in there.

Most sites, if I was lucky enough to find any, suggested that it was using the wrong php.ini. But pear uses (probably) /usr/bin/php.ini

What probably happened was:

1. you didn't specify a '--bindir=/usr/bin' to the new php

2. you didn't copy the new php you created when you compiled php to wherever it's looking for it (/usr/bin/)

If you do a search for 'php' you'll get probably way more listings than you hope. But if you look for phpize, you might find the directory where the new php files reside. run this:

% find / -name phpize
OR
% locate phpize

You can locate as long as you're locate.updatedb has been run since you configured php.

For me, it was in /usr/local/bin. I copied php* to /usr/bin and viola.

Hope this helps.

Friday, December 16, 2005

We're going to have to let you go

Warning: If you have clients, you may have experienced nausea, redness of the neck and face, tight fists, and burning sensation in your seat.

Got some clients you're better off without? Find out if you have any clients like these as Christopher Hawkins details the 11 Clients You Need to Fire Right Now.

Thursday, December 15, 2005

Matt Lehnert kickin' it in NYC



From email source:

quick story you guys might enjoy. went to a party at laurens on
saturday night. about 20 people. half of us went to some random bar,
the other half went to this upscale place called Marquee (davedigital

would definitely know this place). anyways, these 2 pretty girls who
were visiting lauren from texas went to Marquee, i didn't of course

opting for the hole in the wall with $3 beers.
So yesterday morning, lauren calls me and says "Do you know some guy
named Matt Line Hart?" i laugh and say yeah and don't bother to
correct her. she says, well he was at Marquee last night, and hit on one of
the girls from texas all night, danced with her, and then was so drunk he
groped her....she turned around and slapped him, and left.
i said yea yea, i doubt it even though it kinda made sense that he
would be in an upscale club getting trashed after losing the heisman. i told
her i'd believe the story when i saw pictures. wellll, here they are..........

Tuesday, December 13, 2005

Generating new host keys (ssh-keygen)

So, you want to create new host keys...

$> ssh-keygen -t rsa

The new key pair is named /home/<YOUR USERNAME>/.ssh/id_rsa and /home/<YOUR USERNAME>/.ssh/id_rsa.pub. Now copy the new id_rsa.pub key to your account on the remote server. You could do that with this command:

$> scp ~/.ssh/id_rsa.pub USERNAME@REMOTESERVER:.ssh/authorized_keys

Or, you might need the sysadmin to do this for you.

Saturday, December 10, 2005

Ruby syntax highlighting for BBEdit

http://www.barebones.com/support/bbedit/plugin_library.shtml

Friday, December 09, 2005

gzip, gunzip with tar

To pack:
tar cvf - FILE-LIST | gzip -c > FILE.tar.gz

To unpack:
gunzip < FILE.tar.gz | tar xvf -


--
the FILE-LIST is just separated by spaces

Monday, December 05, 2005

EXC_BAD_ACCESS KERN_INVALID_ADDRESS

Seen this lately on your Mac?

EXC_BAD_ACCESS (0x0001)
KERN_INVALID_ADDRESS (0x0001) at 0x67703000

I've seen it a couple of times, and it always gets the same reaction out of me. Holy shit! My hard drive is crashing!

Well, it may be, but more likely it means that a .plist file has become corrupt. People get these in many differnent applications. I won't go into why or how they easily become corrupted.

But there is a quick Solution (from your terminal window):

$> cd ~/Library/Preferences/ ... whatever application it is ... .plist

Find the application's .plist file that is offending and just delete it. Of course, you'll lose all your settings. For instance, if the corrupt file is from Mail (com.apple.mail.plist), then you'll lose your account settings, preferences, etc... it'll be like you installed Mail for the first time.

I'd recommend writing down all the options in your account you can get to before deleting the file.

Friday, December 02, 2005

There is so much of this in the world that is not intentional satire.

http://www.huhcorp.com