Re: CGI::Cache problems in FileBackend.pm

It doesn't say anything more than that in the error message? The actual problem should be listed there, after a semi-colon.

It always writes data to a temp file and then renames to the real file name in order to get atomic updates without using locking.

Comment on Re: CGI::Cache problems in FileBackend.pm

Replies are listed 'Best First'.
Re^2: CGI::Cache problems in FileBackend.pm by Maddy (Initiate) on Apr 21, 2005 at 12:19 UTC
no, but the or in Filebackend.pm applies. I guess that the operating system fails to rename because the file CGI_Cache\content\4\5\3\4534b4c894c4e72ddb0480068c379c5dad798c0e is in use by another process. It seems that this is not multi-user :-( `rename( $temp_path, _Untaint_Path( $p_path ) ) or throw Error::Simple( "Couldn't rename $temp_path to $p_path" );` [download] both files exist and are not write protected or anything else...	[reply] [d/l]
Re^3: CGI::Cache problems in FileBackend.pm by perrin (Chancellor) on Apr 21, 2005 at 12:50 UTC
Most likely it means that it doesn't work on Windows. This is a completely safe operation on unix systems.	[reply]
Re^4: CGI::Cache problems in FileBackend.pm by Maddy (Initiate) on Apr 22, 2005 at 20:46 UTC
Runs fine under FreeBSD (just tested it ) but i need to get this installed on a Windows 2003-Server.	[reply]