Date: Sat, 11 May 1996 15:44:56 -0700 (PDT) From: Jaye Mathisen <mrcpu@cdsnet.net> To: "John S. Dyson" <toor@dyson.iquest.net> Cc: Craig Shaver <craig@ProGroup.COM>, questions@FreeBSD.ORG Subject: Re: inn & mmap Message-ID: <Pine.NEB.3.92.960511154327.10667J-100000@schizo.cdsnet.net> In-Reply-To: <199605092143.QAA00758@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hmmm, I thought there was a consensus that something was flaky if the active file changed size via newgroup/rmgroup messages with MMAP. If I turn off all newgroup/rmgroup processing, then I have 0 problems with the FreeBSD mmap. If I process newgroup/rmgroups, I have problems. Leads me to believe something flaky there. On Thu, 9 May 1996, John S. Dyson wrote: > > > > > > > > > >>>>> Cove Schneider <cove@brazil.nbn.com> writes: > > > > > > > > Has any one run into any problems with inn using mmap under 2.1? > > > > > > Apparently there is a problem with mmap and inn on 2.1. The workaround > > > is - don't use mmap. Fortunately FreeBSD's VM system is very good, so > > > it won't cause much of a performance hit if you don't use mmap. > > > > > > > Can you expand on this? Where did you get the information about mmap > > on FreeBSD causing problems with innd? Is this a problem with the > > FreeBSD implementation of mmap or is innd doing something wrong? > > i.e., can it be fixed? > > > > Thanks for the info, I will reconfigure innd and reinstall. > > > I have been trying to simulate the problem (I have studied the active > file mmap code in INND), to no avail. Additionally, there are > other OSes that fully implement mmap that have problems with INND. > I really don't know where to look -- if ANYONE can simulate the problem, > I would appreciate it. > > John >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.92.960511154327.10667J-100000>