🚀 go-pugleaf

Dennis Jones wrote:

> ...-- just trying
> to get suggestions before I start work on it.  

Very legitimate.

 > I was assuming that any kind
> of file locking being done by the OS would have to be done with some sort of
> internal kernel object, which of course, no other machine would know about.

Heh, the other machine does not lock the file! The other machine askes if
the os will lock the file. There is only one os (on the machine with the file)
that decides. (Well if it is different, I'm wrong.).

>>Isn't appending to a file with fwrite() an atomic process ?

> No, I don't think so, not even for multiple processes/threads on the same
> machine.

But this even is simpler than many processes on one machine!
There are not several threads running then. Only the os that
has to handle requests. That is your server already.

>>Every client could open the file once for a whole session.
>>You do not have to lock. After fwrite() you could flush.
> 
> I would be very suspicous of code that did that.

It would help the discussion if you told why.

>>That would be all.
> 
> Unfortunately, I think there is a lot more to it than that.

You could have named some.

But give it a try. Just make one apllicatio that continuallly writes
a log sentence to the logfile. Then put it on all your computers and let
them run for a while. Tonight you will know.

Hans.

Hans.