Another quiet Sunday evening in Pocatello … all the more so because Nina’s been sick all day and half of last night. It’s probably something she ate. We decided to go out for dinner last night. It was my day to make decisions (I have the responsibility on the odd days and Nina has it on the even days), so I delegated to her. She came back with three choices: Applebees, Sr. Iguana (a pretty good Mexican food place), and Sizzlers. I picked Sizzlers. We got there about 5 p.m. to find the place packed and when we left an hour later, it was mobbed. However, something in the food last night wasn’t right and Nina’s been spending a LOT of time since then sitting on or hugging the porcelain throne. I suspect we won’t go back there for a while. Nina suggested that we could just decide what we wanted to eat, buy it at the grocery store, and cook it here. “Much safer,” she says.

I’ve had to take the SpyCam software offline. This was the software that would take a picture every five minutes and upload it to the weblog. The camera works just fine, but for some reason the SpyCam software is not working anymore. I suspect one of Microsoft’s security patches is causing the problem. I’ll look to see if there’s any other options available. Meanwhile, no more up-to-date picture on the weblog.

The computer issues abound, actually. Because the government has changed the starting and ending dates for Daylight Savings Time, I needed to patch the two web servers here at the house. One of them I use for development and testing and it also provides some other services. The other one is where all the weblogs are running. I felt that i could do a number of things at the same time by upgrading the operating system from Suse 9.2 to Suse 10.3. I ordered in the CD’s and last Thursday night proceeded to do the upgrade on the development server. While the upgrade went fairly smoothly, the web server wouldn’t come up and run correctly. I’ve spent several hours over the past couple of days sorting out the problems and I think that problem is finally solved. Now the database server is throwing several hundred errors each time I try to start it. I won’t be upgrading the blog server any time soon. I think it’d be good to have all the issues worked out before I attempt to do the upgrade. I’ve decided to buy a new web server computer, bring that one up and get everything working, and then migrate from the old server to the new server. That should be an easier transition. We’ll see.