Re: [Summary-Talk] Why is summary so unreliable?

[Jason Linhart <jason@xxxxxxxxxxx>]

On 9/30/04 1:01 PM Bret Baptist (bbaptist@iexposure.com) wrote:

>My company has posted many times to this list with problems of reliability 
>from summary.

I thought, when I didn't get any more communication from you a few weeks 
ago, that the problem was solved. Since that wasn't the case I am happy 
to continue working with you to get it solved once and for all. 
Unfortunately your problem is very tricky to duplicate, so that process 
might well take a little while.

>Do you have a 2.6 kernel to test on?

Yes, though it isn't currently installed on the machine that has enough 
RAM to duplicate your setup. I will work on reconfiguring that system to 
use the new kernel and then run your configuration again.

Is anyone else here running Summary on a Linux 2.6 kernel?

On 10/1/04 1:55 PM Online Services (webmaster@georgeglazer.com) wrote:

>Is there a reason for the rest of us subscribed to this list to have to
>receive all the messages in this back-and-forth conversation between the 
>two of you while it's worked out?

We have been hearing from quite a few people, and have learned several 
things though the discussion on the list. For example we now know that 
Jeff Logan is having similar problems, while several other people are 
running without any problems at all.

However, everyone should keep in mind that posts to this list go out to 
several hundred people. Some of the more detail oriented, or off topic, 
back and forth might be better as private e-mails.

On 9/30/04 1:01 PM Bret Baptist (bbaptist@iexposure.com) wrote:

>So I guess my question is what can be done to make summary less fragile?

There is no way of knowing right now. I have no idea what is going wrong 
with your configuration, and similar problems don't happen for most 
people. We need to work on making my configuration more like yours, look 
for common patterns with other people who are experiencing similar 
problems, and try changing your configuration to see if we can discover a 
work around that avoids the problems.

Based on what I was seeing earlier, your copy of Summary is failing every 
few hours, as if random blocks of the database are getting corrupted out 
from under Summary. Summary is able to recover from most of this 
corruption, but now and then it is serious enough to cause a crash. The 
crashing is not because of anything in particular that you are doing or 
not doing. It is just that the more you use Summary the more likely you 
are to run into a spot in the database that is corrupt and causes a crash.

If you haven't already, you should try the configuration changes I 
suggested two weeks ago (aliases) and tell me what the results of that 
are.

Jason

-----------------
Jason@Summary.Net
-----------------
Dr. Seuss books . . . can be read and enjoyed on several levels. For
example, 'One Fish Two Fish, Red Fish Blue Fish' can be deconstructed
as a searing indictment of the narrow-minded binary counting system.
  -- Peter van der Linden, Expert C Programming, Deep C Secrets
-------------
Go to <http://summary.net/list.html> to update subscription info.