large history: 2GB shared memory limit
Alex Kiernan
alex.kiernan at gmail.com
Mon Jul 12 08:33:17 UTC 2004
On Sat, 10 Jul 2004 17:31:14 -0700, Russ Allbery <rra at stanford.edu> wrote:
> Marco d'Itri <md at Linux.IT> writes:
> > On Jul 11, Russ Allbery <rra at stanford.edu> wrote:
>
> >> Right now, yes.
>
> > BTW, do you have plans of integrating my cnfs64/his64 patches?
>
> Yeah, I think so.
>
> > Some people used to do it a few years ago. I remember using an almost as
> > good solution, mlocking the history files with a little program similar
> > to contrib/mlockfile.c.
>
> I think that requires that you be able to mmap the files (which is the
> problem in this case), but I'm not positive.
>
You do need to be able to mmap them, but you can build a 64 bit
mlockfile & then lock the history files in core, whilst still using
read/write to access those locked pages (at least on Solaris).
--
Alex Kiernan
More information about the inn-workers
mailing list