Flaw in San Diego's water conservation plan

Another letter to the editor:

In your article http://www3.signonsandiego.com/stories/2009/mar/20/bn20water12926/?zIndex=70189 about the mayor announcing his plans for water budgeting, he is missing an important component, the number of members of a household. The water budget is based on water usage in fiscal years 2005-07. Using this is fine as long as other variables remain the same, namely the number of people in a household. Our son was born in May 2007 and since then our water usage has increased to wash his clothes, his cloth diapers and him. While we are doing everything we can to conserve by replacing our backyard with artificial grass and removing our front lawn to replace it with drought tolerant landscaping, not everyone can afford to do that. For families that added a child or even started caring for someone else at home in the last 2 years, this water budgeting needs another variable and that is the number of people residing at a residence. Maybe the mayor and city council will consider this before voting on the plan.

It probably won't get published because I recently had a letter published, but we'll see. I'm going to send this to the mayor as well.

Holiday season in March?

This week was a pretty exciting week for a geek like me. Google Voice was rolled out, iPhone 3.0 was announced, and the hardware for our new Zimbra server shipped. Google Voice, the successor to GrandCentral has lots of cool features. So far I like the SMS forwarding and the voicemail transcription is interesting (it sort of works; it seemed to get a phone number pretty well). The call quality seems decent and the ability to call any number from the web site is also quite useful. I discontinued my GrandDialer application as I don't have any time to work on it. Another developer is working on GV Mobile which looks quite promising.

iPhone 3.0 looks cool and I can't wait to see it released.

The Zimbra hardware means that my company can start moving towards a real email solution; the hosting provider we use is just awful and quite unreliable despite their claims. In addition, running our own email will reduce external bandwidth and give us more control. The downside is, of course, that if there are problems, I can no longer point the finger!

The disappointment this week is that MIMO Monitors has said that supplies for their 740 have been scarce and don't know when they'll be able to get them. I had ordered one to try out. The touchscreen didn't interest me, but the webcam did; they are having problems getting the touchscreens.

Who says hacks don't cause problems?

The other day I had lunch with a friend and a friend of his wanting to get into Mac development. We were talking and this guy said that he admired a company that created "haxies". I said that I really disliked them as their software can cause problems left and right with the system.

The very next day, I got a ReceiptWallet crash report where the user said he pulled down a menu and tried to create a new library. This action is pretty basic and just uses actions in the nib. In this user's case, it caused ReceiptWallet to crash. Normally I would have ignored this and just said it was some fluke, but I decided to dig deeper. Here's the top of the crash report:

Process:         ReceiptWallet [99875]
Path:            /Applications/ReceiptWallet.app/Contents/MacOS/
ReceiptWallet
Identifier:      com.ggtenterprises.receiptwallet
Version:         2.0.9 (2.0.9)
Code Type:       X86 (Native)
Parent Process:  launchd [98]

Fun with multi-homing

We have a bunch of Xserves running Mac OS X server at work. Most of the machines are only using one of the 2 built in Ethernet ports as they are on the LAN. We have 2 machines that are customer facing and we just added a dedicated inbound connection for them. Being the clever person that I am, I decided that to ease the transition between the old and new IP blocks, I'd block the new connection into the second Ethernet port and we'd be good to go. Turns out it isn't that easy with the Darwin kernel. I setup the default connection to be the new network connection and traffic to the new IP addresses worked fine. However, traffic to the old address got hung up. After a lot of investigation, I determined it was due to Asymmetric routing. No problem, I thought, a few commands and it would work. I managed to do this in Linux by following an article, but it wasn't so easy in Mac OS X. Basically the traffic coming in to the old IP block had the responses going out through the other Ethernet interface out over the new IP block. Many routers block this as it kind of looks like an attack of sorts.

OK, so now that I was stuck, what would I do? I spent about 12 hours on this issue and through some magic use of Apache proxies and another server, I was able to get things working. It isn't pretty, but it solves the problem until we can get an A record changed (we have no control over that record).

Lesson learned, really, really, think carefully before deploying Mac OS X as a server; it can be quite frustrating to do things that I believe should be simple. Maybe I expect too much and OS X Server isn't designed for me.