Bug in "FindFirst" ?
lazarus / 64-FPC development

----------------------------------------------------------------------
bonmario · 2018-05-24 06:57

Hi,
sorry for my bad english ....
in the company where I work, we have a Microsoft Windows network.
Unfortunately I do not know the details, because I do not deal with
that.

Today I noticed that, if I recall the procedure below, passing as a
parameter the name of an existing directory on the network, and then I
check the system operators if there is any lock on the directory
passed as a parameter, the result of the check is that directory is
allocated by me.

Quoteprocedure TestFindFirst(WrkDir:String);
var PathInfo: TSearchRec;
begin
  try
    SysUtils.FindFirst(AppendPathDelim(WrkDir) + GetAllFilesMask,
faDirectory, PathInfo);
  finally
    SysUtils.FindClose(PathInfo);
  end;
end;
I think the command they launch to do the verification is "OpenFile",
but I do not know with which parameters.

Has anyone here already verified something like this?

Thanks in advance, Mario