Hello. I'm hoping someone can shed light on this problem and that I'm
just missing something way too obvious to notice.
I have a backup server which was running NetBSD-3, then NetBSD-4, and
finally NetBSD-5. I noticed that my backups began taking 2 to 3 times
longer when I
hello. Following up on my own post, I discovered that I can change
the window size by adjusting the sysctl variable:
net.inet.tcp.recvspace
The table below shows the settings of this variable compared with the
window size I get.
net.inet.tcp.recvspace window size
32768
Hello. thank you for the response. Ok, so in looking at this
further, I find I have more questions regarding this connection and the way
NetBSD operates.
1. Tcpdump says there is an wscale value of 3. Yet, Michael suggests the
shift value is 8. How does one read the wscale value in
On Thu, 23 Dec 2010, Brian Buhrow wrote:
1. Tcpdump says there is an wscale value of 3. Yet, Michael suggests the
shift value is 8. How does one read the wscale value in the TCP options?
A value of 4197 shifted by 3 to the left gets me a window size that looks
right, so I'm a little confused
Check out pkgsrc/graphics/xplot, and
$ tcpdump -r tracfile -S -tt | tcpdump2xplot
$ xplot foo.xplot
and read the README files in the sources. Without doing this, or
reinventing it, you are unlikely to understand what TCP is doing.
If you would like to put up a raw tcpdump (-w, capturing the
On Dec 23, 2010, at 1:48 PM, Frank Wille wrote:
Hi!
A few days ago I learned from Christos that the MI part of cpu_info, i.e.
ci_data, should be exposed when _KMEMUSER is defined, to make vmstat
compile again.
PowerPC is nasty since it needs three different cpu_infos. I think I'm going
On Fri, Dec 24, 2010 at 03:33:05AM +, David Holland wrote:
On Wed, Dec 22, 2010 at 12:41:23PM +, Michael van Elst wrote:
[...]
There are other places in the WAPBL code (and one in UFS1 dealing with
extended attributes) that get vnodes during a mount operation. While
I haven't
