On Wed, Mar 02, 2011 at 12:33:49PM +0100, Otto Moerbeek wrote:
On Wed, Mar 02, 2011 at 10:18:08AM +, Jason McIntyre wrote:
On Wed, Mar 02, 2011 at 10:13:35AM +0100, Otto Moerbeek wrote:
Lets try to make some progress here. This is the diff I have had in
my tree for a while. It
There is no way to tell if the output of ${daemon} contains important
information or not. I think it should at least make its way into the
system log and not be thrown away blindly.
Index: rc.subr
===
RCS file:
On Mon, 7 Mar 2011, Pascal Stumpf wrote:
There is no way to tell if the output of ${daemon} contains important
information or not. I think it should at least make its way into the
system log and not be thrown away blindly.
Makes sense, I'll look into that.
Index: rc.subr
Debugging is enabled with USE_DEBUG not with DEBUG, so change to NUSE_DEBUG.
Index: Makefile
===
RCS file: /cvs/src/lib/libevent/Makefile,v
retrieving revision 1.30
diff -d -u -p -w -r1.30 Makefile
--- Makefile21 Apr 2010
Date: Mon, 7 Mar 2011 17:31:38 -0300
From: Christiano F. Haesbaert haesba...@haesbaert.org
Debugging is enabled with USE_DEBUG not with DEBUG, so change to NUSE_DEBUG.
This is wrong. Please read the assert(3) manual page.
Index: Makefile
Chequea Tu E-mail
=
[IMAGE]
[IMAGE]
[IMAGE]
Este servicio es exclusivo para usuarios Speedy.
Estimado cliente su cuenta de Speedy no ha podido cerrarse con exito ya
que hay problemas con los servidores y hay fallos con el sistema estamos
trabajando para no tener mayores
On Mon, Mar 07, 2011 at 11:00:20PM +0100, Mark Kettenis wrote:
Date: Mon, 7 Mar 2011 17:31:38 -0300
From: Christiano F. Haesbaert haesba...@haesbaert.org
Debugging is enabled with USE_DEBUG not with DEBUG, so change to NUSE_DEBUG.
This is wrong. Please read the assert(3) manual page.
On Mon, Mar 7, 2011 at 3:31 PM, Christiano F. Haesbaert
haesba...@haesbaert.org wrote:
Debugging is enabled with USE_DEBUG not with DEBUG, so change to NUSE_DEBUG.
NUSE_DEBUG doesn't turn off assert.
On Sun, Mar 06, 2011 at 09:12:41AM +0100, Reyk Floeter wrote:
this diff will break chunked encoding and keep-alive connections where
we need to enable splicing for a specified amount of data only and
return for the next HTTP header.
I don't think so. I only set F_SPLICE for RELAY_PROTO_TCP
I do not think splice should be an option that is exposed to
users.
Either the kernel support works, or doesn't.
The option nosplice is useful for performance comparison and
debugging.
+ { nosplice, NOSPLICE },
That is crazy notion. Either it is faster and works, and
On Mon, Mar 07, 2011 at 04:23:08PM -0700, Theo de Raadt wrote:
I do not think splice should be an option that is exposed to
users.
That makes the diff much smaller.
ok?
Index: usr.sbin/relayd/relay.c
===
RCS file:
On Tue, Mar 08, 2011 at 01:00:48AM +0100, Alexander Bluhm wrote:
On Mon, Mar 07, 2011 at 04:23:08PM -0700, Theo de Raadt wrote:
I do not think splice should be an option that is exposed to
users.
That makes the diff much smaller.
Hmm, perhaps too small. There is a session timeout and
I'm not sure whether anybody still cares about this, but currently it is
not possible to read the help files within hack(6). The patch below does
fix this issue and additionally enables the external parser for viewing
the help files, as specified in the man page.
Index: config.h
On Tue, Mar 8, 2011 at 3:07 AM, Simon Nicolussi
simon.nicolu...@student.uibk.ac.at wrote:
I'm not sure whether anybody still cares about this, but currently it is
not possible to read the help files within hack(6). The patch below does
fix this issue and additionally enables the external parser
A Step- By- Step On HOW To Do And WHAT To Do It All.
Start Now : http://good-links.us/immigrate-to-canada.html
15 matches
Mail list logo
