-- Subject: RE: [Declude.JunkMail] Declude 2.0 - crash
--
--
-- We've gone back to 1.82 as well.
--
-- We'll wait again until 2.0 is proven stable. Declude hasn't been like
-- what
-- has been in the past.
--
-- Just to let people know a bit about this -- the source of the crash was
-- identified
Scott, Barry, et al.,
Just a few comments.
First, I am very happy to see the return of the minor version release.
While this might not have been intentional, it is a welcome site since
that means that smaller issues are being addressed outside of the more
major releases. I hope that following
One other thing that also still concerns me is the new licensing
scheme. It seems like this might have been one of the issues, any while
you might be confident that it is working fine now and is supportable, I
really want to know how it works from a flow-chart perspective. For
instance, I
Hi,
Nope, this is 2.0.4 - just checked my root, this was not the only
occurrence. They contacted me, so I'm in the process to collect logs and
configs to send it off.
My Declude.GP1 states:
(Error 5 at 414c99 v2.0.4)
(attempt to read at 0)
(00414C99 0012FF80 (0002 007A0AB0)
, 2005 6:23 AM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Declude 2.0 - crash
Hi,
Nope, this is 2.0.4 - just checked my root, this was not the only
occurrence. They contacted me, so I'm in the process to collect logs and
configs to send it off.
My Declude.GP1
] On Behalf Of John Tolmachoff
(Lists)
Sent: Friday, February 11, 2005 11:30 AM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Declude 2.0 - crash
Andy, just for kicks, can you exclude any scanning of smd, _md, ~md files
and such.
John Tolmachoff
Engineer/Consultant/Owner
eServices
Good reminder for me - Nothing will ever be like it was.
Software development is an insane business. One of the reasons I got out of
it. I've value the support I get from Declude and Sniffer folks. I would
rather pay these guys money to help me fight the bad guys by listening and
trying to
We've gone back to 1.82 as well.
We'll wait again until 2.0 is proven stable. Declude hasn't been like what
has been in the past.
Just to let people know a bit about this -- the source of the crash was
identified pretty quickly. And a change could have been made almost as
quickly to prevent
] Declude 2.0 - crash
We've gone back to 1.82 as well.
We'll wait again until 2.0 is proven stable. Declude hasn't been like what
has been in the past.
Just to let people know a bit about this -- the source of the crash was
identified pretty quickly. And a change could have been made almost
Phone: +1 201 934-3414 x20 (Business)
Fax:+1 201 934-9206
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox
Sent: Saturday, February 12, 2005 12:40 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Declude 2.0 - crash
Hi
10 matches
Mail list logo
