And I'm not missin' a thing,
Watchin' the full moon crossin' the range,
I'm ridin' the storm out, ridin' the storm out
For now, it looks like I've ridden my own particular storms out. icq-t is behaving now, and should no longer be leaking memory now that Jer has fixed etherx. No buzzes have recurred recently. Also, I have further improved the autoconfiguration system, and I'm now using temas's standard macros for Jabber and Etherx configuration. Mucho better!
Webb's stock price is showing signs of life. Of course, I'm in mid-blackout again...not that it would matter, as I need to sell for enough to pay off enough debts that someone will give us a car loan for a Subaru Forester...
Steve's got a meeting in here in a bit. I'll take that opportunity to go over to Costco and get Pamela's scrips, then go home and pick up a bill to be mailed.
Later: The buzz appears to be back. I'm now using fgrep to split up the logfile that resulted, trying to locate where the buzz began and what happened when it did. In the meantime, now two people have reported that bizarro error that kills the transport on startup with a PTH "scheduler internal error," and I haven't the first [REDACTED] idea why it's doing that, because I've never seen it happen myself. Not once. AAARRRGGGHHHH!!!!!!
Slightly later: OK, I have a pretty good idea of why the buzz is happening. PTH_EVENT_SELECT is apparently a pile of crap. Time to rewrite the guts of libicq-erbo so it can export PTH events for each socket it uses. But that's for tomorrow. Still no clue on the other thing, though. Why the [REDACTED] does this have to be so [REDACTED] complicated?!?