The documentation for the WSAIoctl socket routine describes the SIO_KEEPALIVE_VALS
control code as follows:
SIO_KEEPALIVE_VALS
Enables the per-connection setting of keep-alive option, keepalive time, and keepalive interval. The argument structure for SIO_KEEPALIVE_VALS is as follows:
/* Argument structure for SIO_KEEPALIVE_VALS */
struct tcp_keepalive {
u_long onoff;
u_long keepalivetime;
u_long keepaliveinterval;
};
It neglects, however, to define what the time units are.
It strikes me that seconds or milliseconds are
equally likely. Any ideas?
Thanks
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
On NT/2000, the values “KeepAliveTime” and “KeepAliveInterval” as specified in the registry as global keepalive values are specified in milliseconds, so I would imagine that these are as well - it wouldn’t make sense (at least not to me) to have less granularity over these values when over-riding them on a per-connection basis.
Regards,
Ed Lau
MidCore Software, Inc.
900 Straits Tpke
Middlebury, CT 06762
www.midcore.com
----- Original Message -----
From: Peter Craft
To: NT Developers Interest List
Sent: Thursday, February 14, 2002 3:09 PM
Subject: [ntdev] SIO_KEEPALIVE_VALS units
The documentation for the WSAIoctl socket routine describes the SIO_KEEPALIVE_VALS
control code as follows:
SIO_KEEPALIVE_VALS
Enables the per-connection setting of keep-alive option, keepalive time, and keepalive interval. The argument structure for SIO_KEEPALIVE_VALS is as follows:
/* Argument structure for SIO_KEEPALIVE_VALS */
struct tcp_keepalive {
u_long onoff;
u_long keepalivetime;
u_long keepaliveinterval;
};
It neglects, however, to define what the time units are.
It strikes me that seconds or milliseconds are
equally likely. Any ideas?
Thanks
You are currently subscribed to ntdev as: xxxxx@midcore.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Try any UNIX documentation 
----- Original Message -----
From: Peter Craft
To: NT Developers Interest List
Sent: Thursday, February 14, 2002 11:09 PM
Subject: [ntdev] SIO_KEEPALIVE_VALS units
The documentation for the WSAIoctl socket routine describes the SIO_KEEPALIVE_VALS
control code as follows:
SIO_KEEPALIVE_VALS
Enables the per-connection setting of keep-alive option, keepalive time, and keepalive interval. The argument structure for SIO_KEEPALIVE_VALS is as follows:
/* Argument structure for SIO_KEEPALIVE_VALS */
struct tcp_keepalive {
u_long onoff;
u_long keepalivetime;
u_long keepaliveinterval;
};
It neglects, however, to define what the time units are.
It strikes me that seconds or milliseconds are
equally likely. Any ideas?
Thanks
You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Perfect. Thanks Ed.
Pete
----- Original Message -----
From: Ed Lau
To: NT Developers Interest List
Sent: Thursday, February 14, 2002 1:02 PM
Subject: [ntdev] Re: SIO_KEEPALIVE_VALS units
On NT/2000, the values “KeepAliveTime” and “KeepAliveInterval” as specified in the registry as global keepalive values are specified in milliseconds, so I would imagine that these are as well - it wouldn’t make sense (at least not to me) to have less granularity over these values when over-riding them on a per-connection basis.
Regards,
Ed Lau
MidCore Software, Inc.
900 Straits Tpke
Middlebury, CT 06762
www.midcore.com
----- Original Message -----
From: Peter Craft
To: NT Developers Interest List
Sent: Thursday, February 14, 2002 3:09 PM
Subject: [ntdev] SIO_KEEPALIVE_VALS units
The documentation for the WSAIoctl socket routine describes the SIO_KEEPALIVE_VALS
control code as follows:
SIO_KEEPALIVE_VALS
Enables the per-connection setting of keep-alive option, keepalive time, and keepalive interval. The argument structure for SIO_KEEPALIVE_VALS is as follows:
/* Argument structure for SIO_KEEPALIVE_VALS */
struct tcp_keepalive {
u_long onoff;
u_long keepalivetime;
u_long keepaliveinterval;
};
It neglects, however, to define what the time units are.
It strikes me that seconds or milliseconds are
equally likely. Any ideas?
Thanks
You are currently subscribed to ntdev as: xxxxx@midcore.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com —
You are currently subscribed to ntdev as: xxxxx@alacritech.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com