Did no one see my previous message. There was no response to it but
instead the thread continued as if it didn't get through.
We have a page set up which lists the way to report such problems so
that we can track them down. Without that information, it is
impossible for us to track this down.
Fire Development Team
On Feb 8, 2006, at 5:26 PM, Elektron wrote:
> 1. Install snort
> 2. Run snort when not much else is running
> 3. See what funny messages are being sent.
> Alternatively, send in the crash logs.
> On 2006-02-07, at 02:19:45, David Barr wrote:
>> Okay, latest and greatest:
>> 1) I'm chatting with a particular person in AIM, and start getting
>> 2) I stay out of other services, and limit my testing to AIM.
>> 3) I chat with several people who use the AOL AIM client and have
>> no problems.
>> 4) I open a chat with the person in question and crash before I
>> can even send my first message. The time elapsed between my
>> opening a chat with this person and the crash occurring is wildly
>> variable between 0 and about 4 minutes. I'm still working on
>> determining the client this person is using but, for obvious
>> reasons, it's going slow...
>> * I do not yet know what client this particular person is using.
>> * I'm using 1.5.5. If a debug version is available, or if I can
>> dig up a log file, please let me know.
>> David - Offbeat http://dafydd.livejournal.com
>> dafydd - Online http://pgp.mit.edu/
>> Battalion 4 - Burning Man Emergency Services
>> The only thing worse than planning for disaster, is
>> explaining why you didn't.