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!!
Anyone who has been bored enough to talk to me at length knows that I have been fighting an on/off battle against squirells at our house. For those faced with this particular dilemma, if it isn’t mating season, fox scent (uncouth folks will refer to this as fox urine) works like a charm. A few dabbles and doses in strategic places (if at all possible, in a location than the squirells so that they think the predator can pounce down on them) works like a champ. Unfortunately, it is currently the start of mating season, and at least one lone squirell has found his way into our lower attic. That space currently smells rather ripe, but it doesn’t seem to be deterring the little rodent, so I’ve finally broken down and called in a “professional,” i.e. someone willing to crawl up there, lay traps, and come back to get them and release them somewhere far, far away. It is my hope that once the traps are laid, we will be able to call someone in to close the hole, and this will be an end to our squirell-escapades. I’m probably wrong, but I think this is the last place they are coming in from. And to think, as a child I loved the little furry bastages. But when you hear one over your head, chewing on your house that you don’t like anyway but gosh darn it you have to pay the mortage and its all you’ve got, you get at least a touch annoyed.
After a whirlwind of updates to the perl ebuild last week, including auto-.ph cleaning, some issues for those folks brave enough to risk a threaded perl, and syntax fixes, I’ve hit an unfortunate lull in my ability to do Gentoo work. Let’s blame R/L, and more particularly, a hectic work schedule. On my plate for the long weekend ahead: perlpanel clean up; I think there’s a bug out there under the security umblrella; getting the newer gtk2 working (fails 5% of its tests, and states that it’s passing tests it didn’t expect to – gotta love those test harness writers); whatever else people throw at me. Given the proper time on the weekends, I think I’m going to treat my early mornings like a weekly bug-day – not as good as the real thing, but at least some progress can be made.