[EMAIL PROTECTED]> <p05100301b74bf77fd392@[192.168.1.5]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0us
In-Reply-To: <p05100301b74bf77fd392@[192.168.1.5]>; from [EMAIL PROTECTED] on Tue, 
Jun 12, 2001 at 09:45:54AM -0700

On Tue, Jun 12, 2001 at 09:45:54AM -0700, Randall Gellens wrote:
> At 2:37 PM -1000 6/11/01, Clifton Royston wrote:
> 
> >    If it always has to be locked, then that's probably the safest place
> >  to do it.  I may try that out here and see if it fixes things while
> >  waiting for an update.
> 
> The other place to do it, which would be somewhat more efficient, is 
> in pop_updt.c when we decide that the session is in server mode, and 
> all messages are deleted, or spool isn't dirty.

I like your first idea better, because this last depends on the
possible logic paths through the code never changing, and they are
likely to with future optimizations (which is probably how this stopped
working in the first place.)  Doing the "touch" up front, only if the
bKeep_Temp_Drop boolean is set, should be relatively inexpensive; in
the cases where it ends up being redundant it's likely to also be
insignificant relative to the other actual disk updates that need to be
done.

If I can get time today, I'll try to work on coding this shortly.
  -- Clifton

-- 
 Clifton Royston  --  LavaNet Systems Architect --  [EMAIL PROTECTED]
   WWJD?   "JWRTFM!" - Scott Dorsey (kludge)   "JWG" - Eddie Aikau

Reply via email to