Marco van de Voort wrote:
In our previous episode, Mark Morgan Lloyd said:
If multiple, related, programs running on unix (Linux, Solaris etc.)
refer to the same configuration file accessed via a TIniFile, is there
any recommended "good practice" to ensure that they don't try to update
it simu
In our previous episode, Mark Morgan Lloyd said:
> If multiple, related, programs running on unix (Linux, Solaris etc.)
> refer to the same configuration file accessed via a TIniFile, is there
> any recommended "good practice" to ensure that they don't try to update
> it simultaneously?
>
> In
On 15.02.2013 23:54, Mark Morgan Lloyd wrote:
If multiple, related, programs running on unix (Linux, Solaris etc.)
refer to the same configuration file accessed via a TIniFile, is there
any recommended "good practice" to ensure that they don't try to update
it simultaneously?
In the case that I'
Andrew Brunner wrote:
On 02/15/2013 04:54 PM, Mark Morgan Lloyd wrote:
If multiple, related, programs running on unix (Linux, Solaris etc.)
refer to the same configuration file accessed via a TIniFile, is there
any recommended "good practice" to ensure that they don't try to
update it simultan
I would not use INI if the systems are writing data. While I've had
plenty of success reading INI files in parallel - I seem to recall that
the file is just streamed out without regard to which version is on
disk. I think the file is completely refreshed.
I recommend using a DBMS system of s
If multiple, related, programs running on unix (Linux, Solaris etc.)
refer to the same configuration file accessed via a TIniFile, is there
any recommended "good practice" to ensure that they don't try to update
it simultaneously?
In the case that I'm thinking of, I don't anticipate e.g. multi
