Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 59889 invoked by uid 500); 21 Mar 2001 15:40:42 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 59817 invoked from network); 21 Mar 2001 15:40:30 -0000 X-Authentication-Warning: adsl-77-241-65.rdu.bellsouth.net: trawick set sender to trawickj@bellsouth.net using -f Sender: trawick@bellsouth.net To: Ben Collins-Sussman Cc: dev@apr.apache.org Subject: Re: disk i/o problems References: <86u24onkri.fsf@newton.ch.collab.net> From: Jeff Trawick Date: 21 Mar 2001 10:38:18 -0500 In-Reply-To: <86u24onkri.fsf@newton.ch.collab.net> Message-ID: Lines: 21 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Ben Collins-Sussman writes: > Hi all -- I'm getting some weird disk slowdowns on FreeBSD 4.2. Did you by chance look at an strace/truss of your APR app on Linux and FreeBSD to see what APR is doing on your file? Are you using buffered APR file support? > I think we need to investigate APR and see where the "portability" has > gone astray... what system interfaces changed in FreeBSD 4.2 that so > dislike APR's file routines? Anyone have ideas? There really isn't much code to look at for file I/O. But first I think you might want to look at a syscall trace and see if we're doing the right thing. -- Jeff Trawick | trawickj@bellsouth.net | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...