I should have been more specific:

If one lfs server has opened the file for writing and is updating it, and another lfs server opens for reading, will the second server block on the call or does it just ignore it and try again later? I don't want to impact the performance, although I don't think the block would last for more than a few ms.

Will try and see what happens, then grab a sledge hammer if necessary.

There are no locking issues with having multiple processes access the ban file?

Quote :

Are you running multiple different versions of LFS? It's much easier to run multiple instances of LFS in the same directory. This means that ban files and other files are shared across all your servers. Ban in one, ban in all. No coding necessary.

start LFS.exe /config=configfile1.txt
start LFS.exe /config=configfile2.txt

Wow, quick response, thx.

Hmm, will have to check how we are configed, very glad you brought that up. Still need to code for other admin purposes.

[CD] Hex <<< banging head on table while trying to rethink strategy.

When is the ban file read and/or updated by the server? I cannot find any info.

I have written an app to admin the ban files on our servers and want to combine and clean them into one file then redistribute amongst the servers.

Questions:
1. Are the ban files only read upon lfs server restart, or does lfs actively watch the directory for file changes?
2. Does the server update the ban file on the fly as someone is banned or is there some batch processing aka update on shutdown?

My biggest fear is sync'ing and corrupting the ban files and losing them during an update cycle or reading a not fully updated one and therefore not actually banning someone.

[CD] Hex