Paul Durrant wrote On 10/13/06 04:45,:
On 10/13/06, Michael Watz <[EMAIL PROTECTED]> wrote:
I've got a T2000 running Solaris 10 and I'm running into an issue in
which I'm being asked to set the following UDP tunables vi ndd:
ndd -set /dev/udp udp_xmit_hiwat 65536
ndd -set /dev/udp udp_recv_hiwat 65536
I've found that adding these parameter settings to /etc/system does
*NOT* result in them persisting across reboots:
set udp:udp_xmit_hiwat=65536
set udp:udp_recv_hiwat=65536
This is not surprising as you can see in the udp_impl.h source code:
#define udp_xmit_hiwat udp_param_arr[7].udp_param_value
#define udp_recv_hiwat udp_param_arr[9].udp_param_value
So the 'symbols' do not actually exist. Welcome to the nastiness and
confusion that is ndd :-)
Does anyone have any idea what the "right" way to set these parameters
is for Solaris 10?
I don't have a good answer. I can only suggest you write a script to
execute the necessary ndd hackery before running your application.
A benefit of SMF is that /etc/rc[23].d are much less cluttered so
creating a file to set them on boot is a little simpler.
Or create an SMF manifest in site, based off of network-initial or
similar and depending on network-initial, for example. Only thing I
don't know is how to insure it runs in time, i.e. what depends on it,
if anything, such as milestone-singleuser.
Or setting them within the application, instead of system wide.
Granted, only works if you have source to the application.
Steffen
Paul
_______________________________________________
networking-discuss mailing list
[email protected]
