I watch over 2 production machines; the second is just coming on. It
has a lot more memory available to give to frontier. It runs a lot
better. We are wondering if giving the other more will help and will
be trying it as soon as the extra 512MB arrives.

You can't go back to 7.01 very easily because there are kernel glue
for verbs that don't exist in Frontier and instances where they are
used in Manila.

Best pragmatic way to integrity check is to do a save copy.

> >
>>Yes, we are seeing something new (since 8.0.5) on a Mac OS ( which we
>>cannot pin down. About half the crashes are supposedly in webstar
>>but there is always a corrupted heap in Frontier. And a few days ago
>>we had the first serious corruption in a production root in 5 years.
>>(We do a save copy on every root every week.) We suspect that an end
>>user somewhere is the trigger but that's not a useful clue on a busy
>>server.
>
>If there is no cure available soon, can I simply start a 7.0.1
>version of Frontier with the databases that ran with 8.0.5 for some
>time now?
>
>The 7.0.1 seemed to be more stable,
>
>Is there a way to check the integrity of a GDB?
>
>Oliver
>
>--


--

- David Bayly. Programmer and digest reader. dbayly at udena dot ch
Digest Readers do it once a day.

Enclosures

None.  

Replies

None.