Author archives: Mike

Been working in Windows all day (good old reliable Windows ;) ). I'd forgotten how much more worn-in my working environment is here, everything set up for two-key access, everything defaulting to opening in the right directory, every tool winnowed from the pack over years of Darwinian selection, every device "just working", without few if ...

Did rather a lot of cleanup of the code today. Finished a number of "polish" elements (e.g. links upward in the hierarchy, retaining hierarchy names and comments through upload/download cycles, that kind of thing). Confirmed that email alerts do work when the email account is set up.

Last task of the day was sitting down ...

Even updated the viewer to allow for picture-in-picture (though I don't have cable-tv-cables or audio-cables to make that work yet). Linux may be stable and fast, but Windows still has it beat on driver support.

Anyway, back to work; going to be a long day I'm guessing. There's no food in the house (didn't get ...

Well, I spent about 1.5 hours working on getting the new TV card working (about 1/2 hour longer than I'd intended). Unfortunately, to do that I needed to recompile my kernel (gods what a stupid system that is, honestly), and something wound up upsetting the magic that let the tablet work. Have spent almost 4 ...

Found a small leak. Basically I keep a table to all streets with (num,apt) indexing lists of modems at that location (normally only a single modem). The code to do that, however, was assuming that it was starting from scratch (i.e. at system load time), whereas these days the locations are re-loaded every 20 minutes ...

You'll need an SVG browser for this one, but I figure it's about time everyone had one anyway :) .

Bleep. There was a dip at 6 hours, but after 20 minutes or so it started climbing again, so we have an unusable product (demo is still fine, it's been running for 17 hours now).

Worse, though, there was a group that went offline, but I got no email. Of course, I forgot to give ...

Well, it takes approximately 6 hours, but it does eventually reach a steady state for memory consumption. While waiting for it to stabilize I implemented the device-hierarchy. Unfortunately, I'm now seeing hard-hangs every once in a while on my machine (looks like yet another database-driven problem, as it's occurring just after the hierarchy import completes ...

Been working on the memory-leak problem. Problem is, the system is supposed to "leak" memory for ~ 2 hours as it scans each modem and records it's values. I think I may have solved it 2 hours ago, but I really won't know for another hour or more (even then, the rate of the leak ...

As mentioned last night, today's first order of business was to get seach working. At the moment this is limited to searching for modems. One of the key requirements, however (again, none of this actually laid out in the original spec, we just decided on Friday) is that search be such that you can optionally ...