From owner-freebsd-current  Sun Nov 12 11:51:09 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id LAA26574
          for current-outgoing; Sun, 12 Nov 1995 11:51:09 -0800
Received: from chrome.jdl.com (chrome.onramp.net [199.1.166.202])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA26531
          for <current@freebsd.org>; Sun, 12 Nov 1995 11:51:01 -0800
Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.jdl.com (8.6.11/8.6.9) with SMTP id NAA18005; Sun, 12 Nov 1995 13:50:32 -0600
Message-Id: <199511121950.NAA18005@chrome.jdl.com>
X-Authentication-Warning: chrome.jdl.com: Host localhost.jdl.com didn't use HELO protocol
To: Peter Dufault <dufault@hda.com>
cc: current@freebsd.org
Subject: Re: ISP state their FreeBSD concerns 
In-reply-to: Your message of "Sun, 12 Nov 1995 08:50:57 EST."
             <199511121350.IAA00279@hda.com> 
Reply-To: jdl@chromatic.com
Clarity-Index: null
Threat-Level: none
Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code.
Net-thought: If you meet the Buddha on the net, put him in your Kill file.
Date: Sun, 12 Nov 1995 13:50:32 -0600
From: Jon Loeliger <jdl@chrome.onramp.net>
Sender: owner-current@freebsd.org
Precedence: bulk

Apparently, Peter Dufault scribbled:
> > 
> > 1.	A concern that FreeBSD tends to "bind" for brief periods when
> > 	loaded...
> 
> Can this is an IDE issue?  I never saw anything like this until
> I configured an IDE mail server.  That system pauses for seconds
> sometimes, and then continues.  This is running -stable, syscons
> only (no X), no messages logged, etc.  The echo stops going to
> the display, the ethernet activity is stopped, all in all it seems
> to be locked up for three or four seconds.
> 
> We have three SCSI only systems and haven't ever seen this, and
> one IDE system that pauses.

Hmmm....  Curious.  I've got a lame-o IDE 2.0.5-95 0622 system,
and I see some occasional pauses too.  Most notably as I mentioned 
earlier with the "talk" program.  I *thought* I correlated it to
receiving mail one day, but wasn't sure at all...  Since I only ever
run "talk" to the west coast, it could easily be a line probelm at
the ISP on their end.  Has anyone else seen talk display this
freezing-up behaviour?  Do I alone imagine it?  Should I cut back
on my (non-)Bass/Guiness drinking? :-)

jdl