On Tue, 4 Mar 2003 04:04:34 +0200, Alexey Zelkin [EMAIL PROTECTED] said:
Wrong.
BZZZT!
As I stated originally, it's impossible to use 'maxsockbuf' value.
That does not change the fact that an unprivileged user can use up to
`maxsockbuf' bytes of wired kernel memory per socket. That's why
hi,
On Mon, Mar 03, 2003 at 09:12:05PM -0500, Garrett Wollman wrote:
As I stated originally, it's impossible to use 'maxsockbuf' value.
That does not change the fact that an unprivileged user can use up to
`maxsockbuf' bytes of wired kernel memory per socket. That's why the
limit exists.
On Sat, 1 Mar 2003 15:41:18 +0200, Ruslan Ermilov [EMAIL PROTECTED] said:
Seriously, you didn't give any alternative. How does one
knows the maximum allowed limit? By just blindly trying?
Ask for however much you think you actually need, and bleat to the
administrator (or limp along) if you
On Fri, Feb 28, 2003 at 02:31:10PM -0500, Garrett Wollman wrote:
On Fri, 28 Feb 2003 13:06:21 +0200, Alexey Zelkin [EMAIL PROTECTED] said:
Working with Sun JDK network code I have realized a need to provide some
range checking wrapper for setsockopt() in SO_{SND,RCV}BUF cases. Short
walk
Folks,
Working with Sun JDK network code I have realized a need to provide some
range checking wrapper for setsockopt() in SO_{SND,RCV}BUF cases. Short
walk over documentation shown that maximum buffer size is exported via
kern.ipc.maxsockbuf sysctl. But attempt to use this value as maximum
On Fri, 28 Feb 2003 13:06:21 +0200, Alexey Zelkin [EMAIL PROTECTED] said:
Working with Sun JDK network code I have realized a need to provide some
range checking wrapper for setsockopt() in SO_{SND,RCV}BUF cases. Short
walk over documentation shown that maximum buffer size is exported via
