Glad to help, and thanks for the update. I will be curious to know if the files are in fact the result of image processing. It's not necessarily "definitely another source", as some cfimage processing involves no creation of temp files. BTW, my last point about looking at the files should help here, to see just what kind of files these are. At least, if they don't have the look of some image filetype, that may help direct your additional investigation.
But yes, as for possible error handling hiding the real root cause, note that if there's some global or application-level handling, it would be pretty easy to remove it, even if just temporarily. If you observe how often these files are created, and find they are created really often, then it wouldn't take long to leave the error handling off to find out what's happening. (And note that you don't need to be the user running the page that gets the error, to see the error. It would be logged in the application.log.) No offense intended if you already were aware of the above. I never presume what even experienced people may know. Some never dabble much in error handling, for instance. Also, when I offer answers on lists, I am as often answering for other readers, who may benefit from a little more context. It makes my notes a tad longer (and that frustrates some), but I hope the benefit outweighs the risk. :-) Indeed, thanks for your kind regards on my having surmised things. /charlie From: cfaussie@googlegroups.com [mailto:cfaussie@googlegroups.com] On Behalf Of Brett Payne-Rhodes Sent: Tuesday, December 20, 2011 10:20 PM To: cfaussie@googlegroups.com Subject: Re: [cfaussie] CF Temp files Thanks Charlie, As usual you have surmissed much of what is going on quite accurately. There is no danger of this being a DoS attack, the system in question is effectively closed to the outside world. And the system does have a significant amount of activity in terms of files being uploaded. In addition, all images are 'served' via a CF script using CFIMAGE that will most definitely be another source of these temporary files. And given the volume of work being carried out it does not surprise me that so many temporary files are being created. In terms of the log files, I don't see a lot of activity there, especially with regard to file uploads and image serving but then they are wrapped up in cftry/cfcatch so we are not going to know about it via error logging. Which could suggest the issue is hidden. Maybe the 'delete' permission has been removed without us knowing about it? That would mean the temporary files could not be removed and the try/catch would be hiding it from us seeing it as a problem until the disk fills up. Thanks again Charlie, most hlepful! Cheers, Brett B) -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
