Ian Smith wrote:
> > Message: 18
> > Date: Thu, 04 Jan 2007 18:05:27 -0500
> > From: Bob McIsaac <[EMAIL PROTECTED]>
>
> > Doug Hardie wrote:
> > >
> > > On Jan 3, 2007, at 22:57, Bob McIsaac wrote:
> > >
> > >> Problem: Browser status 'looking up address' for 10 seconds for any
> > >> web
> Message: 18
> Date: Thu, 04 Jan 2007 18:05:27 -0500
> From: Bob McIsaac <[EMAIL PROTECTED]>
> Doug Hardie wrote:
> >
> > On Jan 3, 2007, at 22:57, Bob McIsaac wrote:
> >
> >> Problem: Browser status 'looking up address' for 10 seconds for any
> >> web page clicked. Slashdot takes almost
Doug Hardie wrote:
On Jan 3, 2007, at 22:57, Bob McIsaac wrote:
Problem: Browser status 'looking up address' for 10 seconds for any
web page clicked. Slashdot takes almost a minute to load. But FTP
performance is good and running a shoutcast stream is no problem.
Sending mail via my ISP is slo
Josh Carroll wrote:
Problem: Browser status 'looking up address' for 10 seconds for any
web page clicked. Slashdot takes almost a minute to load. But FTP
performance is good and running a shoutcast stream is no problem.
Sending mail via my ISP is slow.
How about a la
Problem: Browser status 'looking up address' for 10 seconds for any
web page clicked. Slashdot takes almost a minute to load. But FTP
performance is good and running a shoutcast stream is no problem.
Sending mail via my ISP is slow.
How about a large transfer over http with fetch or wget? Does
Problem: Browser status 'looking up address' for 10 seconds for any
web page clicked. Slashdot takes almost a minute to load. But FTP
performance is good and running a shoutcast stream is no problem.
Sending mail via my ISP is slow.
Investigation: - "sysctl -a | grep net | less" shows a ton of
