I have been trying to get to the bottom of the zero byte files named CASESENSITVETEST which appear in my tmp directory.
Initially I thought that the timings were random and I tried to see just what might be generating the files and went through the following tests;
1 I went through CMX admin settings and got rid of surplus information for example removing the create local option for the graph files and daily graph files. This made no change to the issue.
2 Next I looked through the CUtils .ini file and nothing there showed up as a potential error point.
3 The last place which ran a timing issue was the crontab files which we use to run data updates for CUtils, the line that I really worked on was the regular updates of UserReports, UserAskedData, and Sysinfo and when I changed the rollover time from 15 mins to 9 mins, 14 mins and 29 mins I could see that the zero byte files were being created at each of the update points leading me to think I may have found the issue.
Next I sequentially removed the various cmd functions to see if any one of them caused the issue but this was not the case. Finally I removed all three cmd functions and the zero byte files still appeared at the update point so essentially the issue is still not solved.
I am not sure where to go next since CMX does not produce a timed effect whereas the crontab updates for CUtils does seem to produce the timed effect but why?
Do you have any thoughts on this or should I just live with the problem and clear the tmp directory from time to time with a RPi reboot.
Hans this is slow non urgent problem.
