This is true, but they are unset and I assume the default values are as noted in the sources. The definitions of ip_ct_udp_timeout and ip_ct_udp_timeout_stream are in seconds so I don't understand the jiffies/seconds conversion requirement.
tedc -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chaskiel M Grundman Sent: Thursday, March 08, 2007 11:40 AM To: [email protected] Subject: RE: [OpenAFS] OpenAFS Client Availability --On Thursday, March 08, 2007 10:28:17 AM -0900 ted creedon <[EMAIL PROTECTED]> wrote: > On Linux sysctl -q ip_ct_udp_timeout_stream gets an unknown key error. > > Where else can I look in the Linux and Freebsd boxes? you want net.ipv4.netfilter.ip_conntrack_udp_timeout, and net.ipv4.netfilter.ip_conntrack_udp_timeout_stream > unsigned int ip_ct_udp_timeout = 30*HZ; > unsigned int ip_ct_udp_timeout_stream = 180*HZ; > in .config CONFIG_HZ_250=y > > so the default values published assume an RTC clock frequency of 1 HZ, > which it is not. the sysctl stuff converts the values between jiffies and seconds as appropriate. There is no need to take HZ into account unless you mangle the variables directly. _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
