Date: Thu, 21 Nov 2002 13:36:47 -0800 (PST) From: John Polstra <jdp@polstra.com> To: hackers@freebsd.org Cc: danderse@cs.utah.edu Subject: Re: Changing socket buffer timeout to a u_long? Message-ID: <200211212136.gALLal5b080934@vashon.polstra.com> In-Reply-To: <20021121123126.E75421@cs.utah.edu> References: <20021121123126.E75421@cs.utah.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20021121123126.E75421@cs.utah.edu>, David G. Andersen <danderse@cs.utah.edu> wrote: > Are there compelling reasons not to change the socket buffer > timeout to a u_long from a u_short? This variable stores > the number of ticks before the socket operation times out. I already changed it from short to int in -current in July. (It has never been unsigned in FreeBSD, as far as I know.) Making it long is overkill since that means it is 64 bits on the Alpha and Sparc64 platforms. I didn't change it in -stable for compatibility reasons, though I doubt it is much of an issue. In -current only netstat and systat needed to be recompiled. I haven't heard about it affecting any ports. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211212136.gALLal5b080934>