fabio rohrich wrote:
Hi all,
I have no a server at home, only a linux station. I'm
writing a module that modify the html content. I have
the problem that I don't know how to simulate the
client server environment. I mean: I can set up a
module in a location (with its handler) and I can see
how
I had a brief conversation with some people on IRC tonight because my svn
import was failing. The error was:
subversion/libsvn_ra_dav/util.c:358: (apr_err=175002)
svn: RA layer request failed
svn: OPTIONS request failed on /foobar
subversion/libsvn_ra_dav/util.c:343: (apr_err=175002)
svn: The
On Mon, Jan 13, 2003 at 02:19:26AM +0100, André Malo wrote:
oh darn, that's a weird definition. Ok, then I think, I'll leave it in
mod_log_config (which uses the api function anyway). Thanks for the hint
;-)
Couldn't this be fixed by either changing the logformat to have - in that
place, or
On Sun, Jan 12, 2003 at 07:31:56PM -0800, [EMAIL PROTECTED] wrote:
...
Notice that a 301 request is a permanent redirect, and the reason for this
redirect is that I requested /foobar, not /foobar/. There are a couple of
problems with this.
1) The error message isn't very good.
Yah :-(
Eider Silva de Oliveira wrote:
Hi,
I don't know if it is the case, I think the best performance solution
to achieve high scalability (10K connections per cpu unit) will be
several sockets being handled by an unique thread, in a way we will have
fewer running thread to attend more sockets
On Mon, 13 Jan 2003, Aaron Bannert wrote:
On Monday, January 13, 2003, at 02:40 AM, Greg Stein wrote:
2) I got this even if I put /foobar/ in my request. I haven't done
enough research to determine if my shell or the svn client was
stripping
off the trailing slash, but something
On Mon, Jan 13, 2003 at 06:46:19AM -0500, Rodent of Unusual Size wrote:
okey, here's anpther take on the %2f thing. as a reminder, we
currently reject any reques that includes an encoded slash in the
pat with a 404. this breaks environments which need to use %2f in
the path info. the issue
At 04:37 PM 1/13/2003, Greg Stein wrote:
On Mon, Jan 13, 2003 at 06:46:19AM -0500, Rodent of Unusual Size wrote:
okey, here's anpther take on the %2f thing. as a reminder, we
currently reject any reques that includes an encoded slash in the
pat with a 404. this breaks environments which need
After starting the server for many times I've received:
[Tue Jan 14 15:55:36 2003] [emerg] (28)No space left on device: Couldn't
create accept lock
I figured out that it was the ipc device that run out of space on the
allocated segment, because I had encountered this problem before.
Is it
