Confirmed here as well... Good on OSX.
On Dec 2, 2010, at 12:19 PM, Sander Temme wrote:
On Nov 25, 2010, at 11:34 AM, Issac Goldstand wrote:
After a year and a half, the apreq team would like to release version
2.13 of libapreq.
Good PGP signature; good md5.
Built and tested on an
On Mon, Nov 29, 2010 at 04:37:49PM -, fua...@apache.org wrote:
URL: http://svn.apache.org/viewvc?rev=1040177view=rev
Log:
Supress compiler warning.
...
==
--- httpd/httpd/trunk/modules/http/http_protocol.c
Is anyone successfully using mod_disk_cache on Windows?
Thanks,
Dan
On Nov 25, 2010, at 11:34 AM, Issac Goldstand wrote:
After a year and a half, the apreq team would like to release version
2.13 of libapreq.
Good PGP signature; good md5.
Built and tested on an x64 Meerkat box, against bundled Apache2.
Build against httpd and apr trunk fails: configure
On 23 Nov 2010, at 8:21 PM, Dan Poirier wrote:
We're seeing errors like this from mod_disk_cache on Windows only:
(OS 5)Access is denied. : disk_cache: rename tempfile to datafile
failed: c:/temp/HTTPServer7/aptmpV0JKJ8 -
c:/temp/HTTPServer7/wHY/FhW/b...@muvttlk@V4w.data
under moderate to
Confirmed here as well... Good on OSX.
On Dec 2, 2010, at 12:19 PM, Sander Temme wrote:
On Nov 25, 2010, at 11:34 AM, Issac Goldstand wrote:
After a year and a half, the apreq team would like to release version
2.13 of libapreq.
Good PGP signature; good md5.
Built and tested on an
On Thu, Dec 2, 2010 at 12:23 PM, Graham Leggett minf...@sharp.fm wrote:
On 23 Nov 2010, at 8:21 PM, Dan Poirier wrote:
We're seeing errors like this from mod_disk_cache on Windows only:
(OS 5)Access is denied. : disk_cache: rename tempfile to datafile
failed: c:/temp/HTTPServer7/aptmpV0JKJ8
On 12/2/2010 11:23 AM, Graham Leggett wrote:
Does Windows allow you to move a file into place while the replaced file is
still open for
read?
This is illustrative of Win32 limitations;
The DeleteFile function fails if an application attempts to delete a file that
is open
for normal I/O or
I'd say I am. Even though it is not a high traffic server, the last time I got
one of those errors was October 8th. looking further back, it is always
following one specific custom error doc that oops, didn't exist till now cause
I forgot to generate a new on when I changed the look of the
