> > You can scream all you want that "it isn't free software" but the fact
> > of the matter is that you all scream that and then go do your slides for
> > your Linux talks in PowerPoint.
>
> I think this is an unfair generalization.
Not really. In Linus's book he describes that his
You can scream all you want that it isn't free software but the fact
of the matter is that you all scream that and then go do your slides for
your Linux talks in PowerPoint.
I think this is an unfair generalization.
Not really. In Linus's book he describes that his presentations used
> You can fix this by upping the socket buffer that ping asks for (look
> for setsockopt( ... SO_RCVBUF ...)) and then tuning the kernel to
> allow larger socket buffers. The file to fiddle with is
> /proc/sys/net/core/rmem_max.
Currently it is set to 65535. I doubled it several times and
You can fix this by upping the socket buffer that ping asks for (look
for setsockopt( ... SO_RCVBUF ...)) and then tuning the kernel to
allow larger socket buffers. The file to fiddle with is
/proc/sys/net/core/rmem_max.
Currently it is set to 65535. I doubled it several times and each
1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
packet loss when doing a ping -f with a packet size of 64590 or higher.
2. A "ping -f -s 64589" to a machine running kernel 2.2.19 results in 0%
packet loss. By incrementing the packetsize by one "ping -f -s 64590" or
1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
packet loss when doing a ping -f with a packet size of 64590 or higher.
2. A ping -f -s 64589 to a machine running kernel 2.2.19 results in 0%
packet loss. By incrementing the packetsize by one ping -f -s 64590 or
higher,
6 matches
Mail list logo
