Archives June 3, 2004

Looks as though the problems with the scanner were being precipitated by having too many simultaneous postgresql queries. Introducing more randomness into the scanner has let it run for a few hours at a time so far. Have begun producing a trivial summary/overview in simple text which makes it possible to confirm that the scanner ...

Looks as though the problems with the scanner were being precipitated by having too many simultaneous postgresql queries. Introducing more randomness into the scanner has let it run for a few hours at a time so far. Have begun producing a trivial summary/overview in simple text which makes it possible to confirm that the scanner ...

I must admit complete and abject defeat. I sent a mock-legalese threatening letter to Lisa wrt her promise to get together and chat. Got back a perfectly formed legal document with threats of litigation, callouts on various poorly formed legal theories, etceteras (no references to case law, however). Shiver. Long and short of the harrowing ...

I must admit complete and abject defeat. I sent a mock-legalese threatening letter to Lisa wrt her promise to get together and chat. Got back a perfectly formed legal document with threats of litigation, callouts on various poorly formed legal theories, etceteras (no references to case law, however). Shiver. Long and short of the harrowing ...

The annoying crashes during the run of the ping scanner appear to be happening in the middle of a huge chain of PyPgSQL calls, particularly ones that appear to be network related. Going to have to check out twisted.enterprise to see if they had to do something special to make PyPgSQL play nice with Twisted's ...