John Aldrich wrote in a message to Roy J. Tellason:
 JA> Sunday March 08 1998 13:19, Roy J. Tellason wrote to John 
 JA> Aldrich: 
 RJT> I find it somewhat confusing to be able to set it up there,  in
 RJT> squish.cfg, and to "set" the bases themselves,  in terms of which of
 RJT> these is going to override other ones.  It appears that setting stuff 
n
 RJT> squish.cfg can override stuff that you do with sqset,  but I'm not 
re.
 JA> Nope. Squish will only "know" what is in the Squish.cfg when
 JA> you initially set up an area. After that, it don't know
 JA> squat if you change the config... 
I've read this before,  but I've also found that there were times when the 
area of interest had been "set" to the value in squish.cfg after I'd gone and 
changed it with SQSET.  Sometimes this has happened more than once.  So when 
I saw it happening,  I went into squish.cfg and took out those definitions,  
and it hasn't happened since.
 RJT> What I've ended up doing here is not specifying any limits at all in 
the  RJT> config files,  and when I first turn an echo on I'll look after a 
while
 RJT> and get a feel for how much traffic it's going to see,  and then pick a
 RJT> time and use SQSET on it once.
 JA> That's a good idea...sorta.... :) Or, you can just set REALLY 
 JA> high limits (like 2000 messages or 10 days or something...) and 
 JA> then if you find it's a slow echo, just reduce the # of 
 JA> messages, etc...
Neither 2000 messages nor 10 days is what I'd call a "really high" limit.  
>
In fact,  most of my stuff by default has a max number limit of 2500 or 5000 
and a time limit of 30 days,  though I'll cut that back if there's a lot of 
traffic in the echo,  like to 14 days or in one or two cases 7 days.
 RJT> The only disadvantage to this is that if you trash a file somehow and
 RJT> need to run SQFIX on it,  you'll want to look at the settings that are
 RJT> in place with SQSET _first_,  fix the file,  and then set it again when
 RJT> you're done.
 JA> Yeah...someone wrote a nice little 4DOS btm file to sniff out 
 JA> and fix bad areas. I do this nightly... :) If you're 
 JA> interested, I'll email it to ya...but you really need to be 
 JA> running 4dos (a command.com replacement...)         
I've got a little batch file here someplace that's supposed to do that,  but 
I never got around to putting it in.  It's one batch file that calls another 
during the pack process,  if I remember right.
I don't usually have any problems with areas getting corrupted,  for the most 
part,  except every once in a while something will do a number on whatever I 
happen to be messing with on the system at the time,  and step all over 
*everything*.  If I'm tossing mail when it happens then those areas involved 
while the glitch comes up will sometimes get trashed,  and I'll know I have 
to fix them.
(BTW,  it's nice to add a little white space like between paragraphs and such 
rather than having everything all jammed together like it was before I put 
some in there...)
email: roy.j.tellason%tanstaaf@frackit.com 
--- 
---------------