On Fri, 15 Jun 2001 [EMAIL PROTECTED] wrote:
>
> > You can fix this by upping the socket buffer that ping asks for (look
> > for setsockopt( ... SO_RCVBUF ...)) and then tuning the kernel to
> > allow larger socket buffers. The file to fiddle with is
> > /proc/sys/net/core/rmem_max.
>
> Curren
Odds are it's a raw socket receive buffer issue. Stock pings only ask for
a ~96k socket buffer, which means that they can only hold one ~64k packet
at a time. So, if you're ever slow grabbing packets out of the buffer,
you're going to drop traffic.
You can fix this by upping the socket buffer
On Wed, 28 Mar 2001, Gregory Maxwell wrote:
>
> Asante:
> FriendlyNet GigaNIX 1000TPC (Cu) $149.99
>
Interesting -- this seems to be the only card of the set that actually has
drivers available for download, although the D-Link card has drivers for
an older GigE card listed.
According to
On Fri, 2 Mar 2001 [EMAIL PROTECTED] wrote:
> > together to put 2.2.18 on this machine. I can't guarantee when I'll
> > be able to do this though.
>
> You planned to make more accurate strace on Monday, if I remember correctly.
> Now it is not necessary, Scott's one is enough to understand that
I have a fairly repeatable rsync over ssh stall that I'm seeing between
two Linux boxes, both running identical 2.4.1 kernels. The stall is
fairly easy to repeat in our environment -- it can happen up to several
times per minute, and usually happens at least once per minute. It
doesn't really s
On 12 Feb 2001, H. Peter Anvin wrote:
>
> Just checked my own code, and SYSLINUX does indeed support 115200 (I
> changed this to be a 32-bit register ages ago, apparently.) Still
> doesn't answer the question "why"... all I think you do is increase
> the risk for FIFO overrun and lost character
On Wed, 31 Jan 2001, George wrote:
>
> If someone says 1 bus, give them one bus.
>
> Just make the description say:
> Add 1 for every PCI
> Add 1 for every AGP
> Add 1 for every CardBus
> Also account for anything else funny in the system.
>
> Then panic on boot if they're wrong (sort of
Is syslog running correctly? When syslog screws up, it very frequently
results in this sort of problem.
Scott
On Mon, 8 Jan 2001, Chris Meadors wrote:
> On Mon, 8 Jan 2001, Igmar Palsenberg wrote:
>
> > check /etc/pam.d/login
>
> No pam.
>
> > Could be kerberos that is biting you, althrou
It works if you compile the kernel with the processor type set to Pentium
II or higher, or disable RAID5. I've been meaning to report this one, but
2.4.0 was released before I had time to test the last prerelease, and I
haven't had time to test the final release yet.
Scott
On Sun, 7 Jan 2001,
On Fri, 5 Jan 2001, Michael D. Crawford wrote:
>
> You're probably not going to have much luck getting any source off any servers
> tonight. Might I suggest you pop over to Slashdot and give the clueless some
> clues on getting their new kernels working? They need help.
Dunno -- my mirror (ft
10 matches
Mail list logo
