Re: Exclusive file access

[ahlan@marriott.org]

On Thursday, August 27, 2015 at 3:52:36 PM UTC+2, ah...@marriott.org wrote:
> Dear All,
> 
> Obviously I'm misunderstanding something here.
> 
> I thought that if two processes tried to open the same file for write access then the second process would get an exception.
> 
> I have a simple example which when compiled using GnatPro 7.3.1 and run under 32-bit Windows XP demonstrates that this is not so.
> 
> Which then begs the question on how to detect if the file is in use and abort if it is.
> This should be simple but obviously too complex for my tiny brain.
> Does anyone know how to do this from Ada (without resorting to the OS directly)?
> 
> My simple test program is
> 
> package body Test is
> 
>   package Io renames Ada.Text_IO;
> 
>   procedure Work is
>     The_File : Io.File_Type;
>   begin
>     Io.Open (The_File, Io.Out_File, "Test.Txt");
>     for Count in Natural'value(Ada.Command_Line.Argument(1)) .. Natural'value(Ada.Command_Line.Argument(2)) loop
>       Io.Put_Line (The_File, "Count =" & Count'img);
>       Io.Put_Line ("Count =" & Count'img);
>       delay 1.0;
>     end loop;
>     Io.Close (The_File);
>   exception
>   when others =>
>     Io.Put_Line ("Exception");
>   end Work;
> 
> end Test;
> 
> If I execute this from one process with parameters 1 10 and then when it reaches 8 start the program again from a second process with parameters 3 7 on the same machine, the resultant file is a nice mixture! :-(
> 
> Count = 3
> Count = 4
> Count = 5
> Count = 6
> Count = 7
> Count = 6
> Count = 7
> Count = 8
> Count = 9
> Count = 10
> 
> This is not what I want. I want what the first instance produces and the second instance to fail. Surely nobody would want otherwise ;-)
> 
> Best wishes,
> Ahlan

I have no idea about Linux but it is perfectly possible under Windows. However this doesn't stop people (including Microsoft) from creating lock files that then sometimes get left behind when a program crashes rendering the file locked forever! So the presence of lock files doesn't mean that the opsys can't lock exclusively.
I mentioned a logger not because I want to write a logger but as a simple example of somthing someone might want to write.