I like the functionality added and that the timeout is configurable via a command line option. However, I would prefer to have the default off... But I leave the decision up to you.

I guess I was not clear enough what the issue is that I'm trying to address. I'm not trying to get the script running. It was just used to demonstrate the issue.

I'm fine with the SCTP related changes.

OK, I tested this patch and think it is OK to commit under the assumption of removing the sysctl variable net.inet.tcp.maxunacktime.

In D14993#320689, @jtl wrote:

In D14993#320674, @tuexen wrote:

I'm not sure it is a good idea to have a sysctl for the default value. I would prefer to have the default value always be 0 (not changeable by a sysctl) and required the application to set a non-default value via the socket option. Why is there a need to change the default from "off" on a system wide base?

I don't have a particular use case. I assumed it might be easier, in some environments, to change the default rather than change the application code. However, I don't feel strongly that we need to support a non-0 system-wide default.

I'm not sure it is a good idea to have a sysctl for the default value. I would prefer to have the default value always be 0 (not changeable by a sysctl) and required the application to set a non-default value via the socket option. Why is there a need to change the default from "off" on a system wide base?