From owner-freebsd-current Sun Jul 20 16:49:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA08323 for current-outgoing; Sun, 20 Jul 1997 16:49:33 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA08314 for ; Sun, 20 Jul 1997 16:49:28 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA10089; Sun, 20 Jul 1997 16:47:10 -0700 From: Terry Lambert Message-Id: <199707202347.QAA10089@phaeton.artisoft.com> Subject: Re: -current :) To: dk+@ua.net Date: Sun, 20 Jul 1997 16:47:10 -0700 (MST) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199707192222.PAA22048@dog.farm.org> from "Dmitry Kohmanyuk" at Jul 19, 97 03:22:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ ... inserted NUL's ... ] > > FWIW: I have been able to repeat this with vi and files in frags. You > > have to do all of the following before updated fires. > > over NFS, right? No. To local disk. It seems related to the last series of VM changes (quite a while back, I'm afraid). I have not been able to repeat it reliably without a huge amount of work in my test case. It seems related to zero fill of partial pages when frags are in use, and the resulting change to the frag does not result in the dirty page being treated as if it were really dirty. I can't be more specific than that without a lot more work, unfortunately. > btw, which LDAP server, ldapd from UMICH? Yes. It has a number of problems, including that it does not interoperate with the 30 eval LDAP browser for Windows 95, and that by default it wants ndbm, which FreeBSD pretends to support, but doesn't. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.