Christian Biere wrote:
> Matthew Lye wrote:
> > I've been getting fairly frequent messages like this, recently:
> > > 07-12-07 18:42:15 (WARNING): unable to set TCP_NODELAY on fd#102:
> > > Invalid argument
> It probably means TCP_NODELAY is already enabled on the socket. Can or
> rather will h
Matthew Lye wrote:
> I've been getting fairly frequent messages like this, recently:
> > 07-12-07 18:42:15 (WARNING): unable to set TCP_NODELAY on fd#102:
> > Invalid argument
It probably means TCP_NODELAY is already enabled on the socket. Can or
rather will happen with TLS connections. I'd ex
by the way:
I've been getting fairly frequent messages like this, recently:
> 07-12-07 18:42:15 (WARNING): unable to set TCP_NODELAY on fd#102:
> Invalid argument
My build is a day or two old. It could be a Leopard thing.
- Matt
-
