In case anyone at all cares about the battle against the Squirrel Menace…we finally got someone out here to put down traps. It was a warm, sultry 50 that day. The next day it was below 30 and we got a good 6 inches or more of snow, burrying the traps. Figures. My heart was broken, the squirrel(s) were flaunting their ability to make tracks alongside the traps as they (she?) went in and out of my attic, and I was facing another long, drawn out fight to free my roof. Then yesterday, when the snow melted, I looked up and behold I did see the glory of the trap at work! That’s right kids, we’ve caught ourselves a real, in the fur squirrel. Now to get someone out here to patch that hole before her cronies attempt to move in. Not to mention getting the catcher back out here to remove the scrambling, irate squirrel from our roof.
Not that there are probably anyone looking at this site, but given that most of my herd is awol or otherwise committed (and we aren’t that big a herd to begin with), I thought I’d at least put into writing what I’ve been musing over. First off, I’d like to unmask perl 5.8.6. Been marked ~ for way too long in my opinion. But before doing that, I’d like to go through the tree and finally mark those ebuilds that are superceded by the 5.8.6 core install, which should not only help with minimizing overrides, but should also lay the groundwork for breaking up the dev-perl tree (finally).
After months of not having the time to work on it, I finally just sat down this last week and did it. I’ve gotten most of the bugs worked out now. Wish I could grok a way to load/access all of these conf files without hammering the running size of the job, since the cron engine piece sits in memory once started. To sum up what it does (since no one probably knows), sv connects to a website and does some validation – from as simple as a Big Brother-esque “is it up” all the way down to confirming that a navigation path through the site is functional. Would still like to get it reload those confs as needed, but I think my first problem is memory management. I know, in an age where its so cheap to get a few hundred megs of ram, what’s a few processes running at 4 megs a piece, right? But I’m not satisfied with that answer – for starters, its running at 4megs with only 6 validations running. If we bump this to include all of our old Big Brother clients, then that number could grow, and then it would be a problem. Ugh. My kingdom for a simple memory safe method for getting this data out!!