🚀 go-pugleaf

In article <829872205snz@siberia.demon.co.uk>
           philip@siberia.demon.co.uk "Philip McNab" writes:

> On Thursday, in article <829827671snz@wash.demon.co.uk>
>      john@wash.demon.co.uk "John Washington" wrote:
> 
> JW> Same comments also apply to SnzPrune.  I've been a bit fearful
> JW> ... I have the impression that
> JW> space reporting is erratic on some combinations of [waves hands].
> JW> Not sure if it's BC++ 3.1 run time, which OS, or what.
> JW> More detail, anyone?
> 
> I've only heard of this prob on compressed drives: their ideas of
> free space seem pretty random.  I believe you can see 4Mb free and then
> run out of space adding a file of only a few hundred K.  I haven't
> really tried this, because I religiously remove compression from
> drive I find it on.

When I tried compression (Just say NO!, kids) I wouldreliably run out of
disk space when dir reported about 1.2Mb free.  It was really quite consistent
about it.  What happens to Unbatch in this situation ?

Surely it must be possible to make EXPIRE not mess up the indices when it
does run out of space ?  That is the main concern, really.

.splitbung
-- 
* TQ 1.0 * The 'Just So Quotes'.
"Many people would rather die than think; in fact, most do."
        -- Bertrand Russell