[28] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: Expunging old files

daemon@ATHENA.MIT.EDU (Dorothy Bowe)
Tue Mar 15 08:42:18 1994

To: "Richard Basch" <basch@MIT.EDU>
Cc: release-77@MIT.EDU, op@MIT.EDU
In-Reply-To: [26]
Date: Tue, 15 Mar 94 08:42:03 EST
From: Dorothy Bowe <dot@MIT.EDU>


Everything which follows here is my own (limited) understanding of the
problem.  I'm sure folks will free to step in and correct me where I go
wrong.

In any case, as I understand it, expunge has not been running, or at
least not completing, for several months now.  Expunge was designed to
run under NFS where it could run on each file server; it now currently
runs on a single server, something which is just not working.  We know
that, if we want to keep running expunge, we have to change the way it
runs.  While there have been several different solutions tossed around
(I know of at least 3 now), there is no general consensus.  Some of the
solutions require release changes; others do not.

From the release team's point of view, this sounded like something which
would be good to investigate.  However, without knowing the details and
consequences of what was being proposed, we did not feel that we could
recommend that it be included in the release.  On the other hand, it
might be a good idea to get resources to scope out the problem and it's
ramifications to see if we can include it in this or a future release.

 > How does (ii) work?
 > I am concerned that the ramifications have not fully been considered.

I must confess that I'm not sure it does, or that a full design has
been considered.  This was one of the ideas I had heard as of last week.
People other than myself can probably better address your concerns about
the ramifications of any proposed solution, so I won't even try.

		./dot


home help back first fref pref prev next nref lref last post