BUG: iSiloXC ate my .ixl!

[Steve King]

I just encountered a bug where iSiloXC destroyed my .ixl file, truncating it to zero-length. I run the program hourly from crontab like so:

/usr/local/bin/iSiloXC -q -u -x ~/Documents/daily.ixl

It just so happened that my disk was full at the time the cron job ran. It looks like iSiloXC tried to update the status by opening the .ixl for writing (effectively truncating it) and then found it couldn't write because the disk was full. Poof, there goes my data.

For safety's sake, it's common to write data to a temporary file, then deleting the original and renaming the temp file if and only if the write was successful. Can this be incorporated into the next release, please? For now I simply removed the '-u' flag to stop the update.

[iSilo]

We will incorporate your requested change into the next update whereby a temporary file will be created first and then only if that is successfully created will an attempt be made to overwrite the original file.

However, it seems that a better workaround for you would be to place the .ixl file on a drive with plenty of free space rather than removing the -u option if updating is important.