Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!cmcl2!beta!hc!ames!sdcsvax!sdcc6!bparent
From: bparent@sdcc6.ucsd.EDU (Brian Parent)
Newsgroups: comp.unix.wizards
Subject: sun-3 client from sun-2 server, followup
Message-ID: <3255@sdcc6.ucsd.EDU>
Date: Mon, 13-Jul-87 18:59:24 EDT
Article-I.D.: sdcc6.3255
Posted: Mon Jul 13 18:59:24 1987
Date-Received: Wed, 15-Jul-87 01:21:58 EDT
Organization: University of California, San Diego
Lines: 43
Keywords: sun nd client server


Thanks for all the suggestions.  Most of all, thanks to Mark Plotnick who
writes:

>If your sun-2 is using a 3com ethernet controller,
>the sun-3 will flood it with packets faster than it can receive them.
>use adb to patch the window size, ndclient_maxpacks, in
>/pub.MC68020/vmunix to 1 or 2  (it's 6 by default).  or use an ie
>controller in the sun-2.

This works.  I'm currently using 2 and in ~4 days of use have seen not one
message complaining about the nd disk server not responding.

Let me add some details of the patching procedure for those not so familiar
with kernel patching (myself included). (Wizards, please excuse the obvious.)

To get the address of the variable in the kernel, I used:
	% nm vmunix | grep maxpacks
	0f061dc8 D

Then adb the kernel:
	% adb -w vmunix
ask for the value at that address:
	0f061dc8?D
	_ndclient_maxpacks:
	_ndclient_maxpacks:		6
change the value:
	.?W 2
	_ndclient_maxpacks:		0x6		=	0x2
check value again:
	.?D
	_ndclient_maxpacks:
	_ndclient_maxpacks:		2
and you're done.

Again, I'm thankful for your collective help.

(Recently, I've found out that this is a known bug among the folks at Sun, 
but their database pointed to changing Maxpacks for the server via nd.local
commands, not the ndclient_maxpacks variable in the client's kernel.  After
talking to Sun software support, I'm sure they'll update their database.)

-Brian Parent