On Fri, Jan 8, 2010 at 10:57 AM, Jason King <[email protected]> wrote:
> > The problem is, the code that broke was basically unchanged for months. I > went to go run a script that uses this code, and it hung my server up. I > started drilling down to isolate it, and I found the cffile code I > mentioned. Commenting it out prevented the server from hanging. I went to a > backup, copied the exact same lines of code, and pasted it over the 'bad > code', and shazamm! It works. I compared the bad code to the good code, > which should have been the same since the script was untouched since I last > did the backup, and it's identical. > I was actually asking if the CFFILE operation was writing to a network resource, but it sounds like this is a different problem altogether. I'm afraid I don't have any ideas other than perhaps try editing the file directly on the server itself (using vi or whatever) and see if that has the same effect? Then at least you'd have it narrowed down to something going on with your editor if editing with vi directly on the server works. Reason I asked about writing to a network resources is because I recently ran into an issue with PDFBox taking forever to write to a network drive so I thought that might be an avenue of investigation. I suspect in our case it's a network issue of some sort but it was a variable that came to mind. -- Matthew Woodward [email protected] http://mpwoodward.posterous.com identi.ca/Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html
-- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
