tcp_ip_abort_cinterval keeps changing

[Neville Lawrence]

Hi,

We have tcp_ip_abort_cinterval set to 60000 in nddconf. See below:

TRANSPORT_NAME[8]=tcp
NDD_NAME[8]=tcp_ip_abort_cinterval
NDD_VALUE[8]=60000

On reboot of the server the parameter behaves itself and is set at 60000. However about an hour after the server has been booted it reverts back to the default of 75000. See below:

$ ndd -get /dev/tcp tcp_ip_abort_cinterval
75000

Has anyone got any suggestions?

Thanks

[J. Bravo]

Hi:

It sounds very strange... Do you have saved a copy of nddconf under /etc/rc.config.d/ directory?

Regards;

J. Bravo.

[Neville Lawrence]

There is an old copy from before my time here, however it makes no reference to tcp_ip_abort_cinterval.

[J. Bravo]

Hi!

Move that file out of /etc/rc.config.d/ and try it again. 75000 is the default value for that parameter, then if the rc.config sources the backup file after the nddconf the parameter is unset from 60000 to 75000.

Regards;

J. Bravo.

[J. Bravo]

Hi!

If you don't have planned a reboot of the server, you can apply the new file by executing "ndd -c" Then, you can check if the parameter reverts back or not.

Regards;

J. Bravo.

[Neville Lawrence]

OK I have moved the old file out of the way. When I run ndd -c it does revert it back to 60000, however after I have rebooted it reverts back to 75000.

[J. Bravo]

Hi:

When you change the value manually with ndd -c, it reverts back too?

Regards;

J. Bravo.

[Neville Lawrence]

No it appears to stay set at 60000

[J. Bravo]

Hi!

Could you please attach your nddconf file?

Regards;

J. Bravo.

[whiteknight]

Neville,

What is your ARPA transport patch level ?
If it is old, please update it.

PHNE_35351 11.11 cumulative ARPA Transport patch

WK

[J. Bravo]

Hi again!

I think that some application could be executing a ndd after the net starts, please check the rc*d directories and inittab.

Regards;

J. Bravo.

[Laurent Menase]

Hi Neville,

if ndd -a is made, or /sbin/init.d/net.init start
or /sbin/rc2.d/S008net.init start
it can do the same.

ndd -c being made by /sbin/init.d/net

I double check that only ndd could make such change.

[Laurent Menase]

It is also easy if you want to make panic the system when this parameter is changed with a little adb command.