Problem with inifile.fp under Linux

Question

Hello all,
I noticed a problem with inifile.fp under Linux: I can't write the updated
ini file !
hConfigFile = Ini_New(0);
if (Ini_ReadFromFile (hConfigFile, ConfigPath));
Ini_GetInt(hConfigFile, "Client", "ChartsRefreshRate", &ChartsRefreshRate);
Ini_GetInt(hConfigFile, "Client", "ChartsDuration", &ChartsDuration);
.... Change the values ...
Ini_PutInt(hConfigFile, "Client", "ChartsRefreshRate", ChartsRefreshRate);
Ini_PutInt(hConfigFile, "Client", "ChartsDuration", ChartsDuration);
if (0!=(Err=Ini_WriteToFile (hConfigFile, ConfigPath)))
fprintf(stderr, "\nWarning: problem writing %s configuration files: %s",
ConfigPath, GetUILErrorString(Err));
This fails and displays:
Warning: problem writing Config.ini configuration files: File not found
But not only that, it also deletes the ConfigPath file !!!
Which is rather unacceptable !
I see that the inifile.fp I have on the PC (CVI 8.5) is different than the
one I have on the Linux install (cvicc 8.0). Can I copy all the inifile.*
files to Linux or is it more complicated than that ?
Guillaume Dargaud
http://www.gdargaud.net/

Answer 1

Hello Luis,
I came here to check if a new version of CVI (cvicc, not the real-time
module) for Linux had come out and, sadly, it appears that's still not the
case...
But I saw your followup to our original discussion.
The ini file has grown tremendously since then, but I think I had the
problem with even the most basic file: simple name (same directory, no
path), but maybe it was on an NFS directory (that's no longer the case).
Also the fact that instead of writting _in_ the file (where permission was
allowed) you wrote to a temp file (that may not have had permission) and
then renamed accordingly...
I'll start a new project soon that will require ini files, so I'll test it
again.
> (I realize it has been a while, but I thought I'd ask anyway, in case you
> still remember this).  
> I was investigating this bug today, but so far I haven't been able to
> reproduce it. I tried it in both Windows and Linux, with both a
> writeable location for the test .ini file and a non-writeable location,
> but so far the behavior is as expected. Ini_WriteToFile does return an
> error when the location isn't writeable, but it doesn't delete the file.
>   So I was wondering whether this might be related to the specific
> path you were using, or maybe even with the content of the .ini file
> itself. I don't suppose you would remember whether there was anything
> unusual about the path, would you? Also, do you happen to still have this
> .ini file lying around somewhere and wouldn't mind sharing it with me?
>   Luis
Guillaume Dargaud
http://www.gdargaud.net/