The May issue of MacTech magazine is now shipping to subscribers and being found on newsstands. More good stuff this month from all involved. If you are a Mac freelancer, consultant, programmer or involved with the Mac in any way, subscribe, subscribe, subscribe.

Destroy that data when you're done with it!

If you're on a large business network, or have a single laptop, backing up your data is critical...and my recent near-miss. A tiny backup guide.

Speculation and emotion on Apple’s Intel chip switch.

I say that I like dealing in facts, and the only fact that remains is this: there’s only one person who knows all of the details to this arrangement: Steve Jobs. Everyone else is just guessing. Some may have better educated guesses than others, but they’re guessing none-the-less. Here’s my guesses on the matter

Why did this happen? Overall, I want to convince everyone that is isn’t a bad thing. But first, to the speculation:

How to determine what process is listening to a port under OS X

Many times, people are confused when they try to run a program, and it tells them that it can’t bind to a port because the port is already in use. How can you figure this out? First, like most good things, you have to open up Terminal.app.

Once there, you need to use sudo, or get root through su.

The quickest way to see if a port is in use is to use netstat and grep. Let’s say were looking for port 80:

$ netstat -an | grep 80
tcp4 0 0 *.80 *.* LISTEN
2a0c880 stream 0 0 2c02f78 0 0 0 /private/var/run/cupsd