On Mon, Jun 11, 2001 at 03:53:50PM -0700, Randall Gellens wrote:
> It sounds like the bug is that the file isn't touch()ed when
> keep-temp-drop is set, which is the only case where it matters. This
> is very different from the file not being created or locked. It's
> still a bug, just much less serious.
I thought that was what I had said, but I looked back at my original
message, and saw I had written that it wasn't "created or touched",
which includes two totally different cases. Now I understand why you
were taking issue with my statement!
Yes, the only issue is that it is not being touched. I think I must
have been distracted while editing that paragraph.
> > I'm not quite sure of the best place to fix it, though.
>
> The code in that area can be tricky.
I'll say - makes my head spin, and I read it carefully last year when
installing 3.x.
> Probably the thing to do is
> touch() the file just after flock(), but that's off the top of my
> head, without looking at the code. I think we have our own touch()
> routine, but I'd have to check.
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.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED]
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
