NNRPd "option"?
Clayton O'Neill
coneill at oneill.net
Thu Jul 15 00:10:10 UTC 1999
Well, it's obviously not the history file being mmaped. Unfortunately
lsof only displays the size of the file, not the size of the mmap. Does
FreeBSD have something that will give you that info?
On Wed, 14 Jul 1999, The Hermit Hacker wrote:
>
> Like this:
>
> hub# /usr/local/sbin/lsof -p 8131
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> nnrpd 8131 news cwd VDIR 4,131080 512 15872 /news/spool/articles
> nnrpd 8131 news rtd VDIR 4,131072 1024 2 /
> nnrpd 8131 news txt VREG 4,131116 765839 110602 /news/admin/bin/nnrpd
> nnrpd 8131 news txt VREG 4,131076 63884 17427 /usr/libexec/ld-elf.so.1
> nnrpd 8131 news txt VREG 4,131076 633529 24880 /usr/lib/libperl.so.3
> nnrpd 8131 news txt VREG 4,131076 115780 24660 /usr/lib/libm.so.2
> nnrpd 8131 news txt VREG 4,131076 514271 24706 /usr/lib/libc.so.3
> nnrpd 8131 news txt VREG 4,131076 12965 24623 /usr/lib/libdescrypt.so.2
> nnrpd 8131 news txt VREG 4,131076 31723 24835 /usr/lib/libutil.so.2
> nnrpd 8131 news txt VREG 4,131128 105512960 3 /news/spool/articles/disk_one/ctrl_one
> nnrpd 8131 news txt VREG 4,131128 3791519744 5 /news/spool/articles/disk_one/main_one
> nnrpd 8131 news txt VREG 4,131152 3892844570 3 /news/spool/articles/disk_four/main_two
> nnrpd 8131 news txt VREG 4,131144 3897032704 3 /news/spool/articles/disk_three/main_three
> nnrpd 8131 news txt VREG 4,131096 4083759218 4 /news/spool/articles/disk_six/alt_two
> nnrpd 8131 news txt VREG 4,131087 3978645401 3 /news/spool/articles/disk_five/bin_one
> nnrpd 8131 news txt VREG 4,131120 4087576637 3 /news/spool/articles/disk_seven/bin_seven
> nnrpd 8131 news txt VREG 4,131080 2949128 87297 /news/spool/over.view/group.index
> nnrpd 8131 news txt VREG 4,131136 442207 299363 /news/spool/over.view2/a/b/p/e/t/f/alt.binaries.pictures.erotica.teen.female.DAT
> nnrpd 8131 news txt VREG 4,131136 684932 368963 /news/spool/over.view2/a/b/m/e/alt.binaries.multimedia.erotica.DAT
> nnrpd 8131 news txt VREG 4,131136 281011 414047 /news/spool/over.view2/a/b/p/e/f/alt.binaries.pictures.erotic.female.DAT
> nnrpd 8131 news txt VREG 4,131136 789509 414057 /news/spool/over.view2/a/b/p/e/f/alt.binaries.pictures.erotica.female.DAT
> nnrpd 8131 news txt VREG 4,131136 63744 414058 /news/spool/over.view2/a/b/p/e/f/alt.binaries.pictures.erotica.female.IDX
> nnrpd 8131 news 0u inet 0xcd1712a0 0t0 TCP news.trends.ca:nntp->news.trends.ca:4411 (ESTABLISHED)
> nnrpd 8131 news 1u inet 0xcd1712a0 0t0 TCP news.trends.ca:nntp->news.trends.ca:4411 (ESTABLISHED)
> nnrpd 8131 news 2u inet 0xcd1712a0 0t0 TCP news.trends.ca:nntp->news.trends.ca:4411 (ESTABLISHED)
> nnrpd 8131 news 3u unix 0xcd0745a0 0t0 ->0xcd05cf00
> nnrpd 8131 news 4r VREG 4,131128 105512960 3 /news/spool/articles/disk_one/ctrl_one
> nnrpd 8131 news 5r VREG 4,131128 3791519744 5 /news/spool/articles/disk_one/main_one
> nnrpd 8131 news 6r VCHR 2,2 0t0 6293 /dev/null
> nnrpd 8131 news 7r VREG 4,131152 3892844570 3 /news/spool/articles/disk_four/main_two
> nnrpd 8131 news 8r VREG 4,131144 3897032704 3 /news/spool/articles/disk_three/main_three
> nnrpd 8131 news 9r VREG 4,131096 4083759218 4 /news/spool/articles/disk_six/alt_two
> nnrpd 8131 news 10r VREG 4,131087 3978645401 3 /news/spool/articles/disk_five/bin_one
> nnrpd 8131 news 11r VREG 4,131120 4087576637 3 /news/spool/articles/disk_seven/bin_seven
> nnrpd 8131 news 12u VREG 4,131080 2949128 87297 /news/spool/over.view/group.index
> nnrpd 8131 news 13u unix 0xcd067b40 0t0 ->(none)
> nnrpd 8131 news 14u VREG 4,131136 789509 414057 /news/spool/over.view2/a/b/p/e/f/alt.binaries.pictures.erotica.female.DAT
> nnrpd 8131 news 15u VREG 4,131136 63744 414058 /news/spool/over.view2/a/b/p/e/f/alt.binaries.pictures.erotica.female.
>
>
> On Wed, 14 Jul 1999, Clayton O'Neill wrote:
>
> > I seem to recall that I ripped that code out a long time ago. I'd suggest
> > getting a copy of lsof and seeing what is mapped and how big. Or does
> > FreeBSD have something similar to Solaris's pmap?
> >
> > On Wed, 14 Jul 1999, The Hermit Hacker wrote:
> >
> > >
> > > Morning...
> > >
> > > Since upgrading to INN 2.3, my FreeBSD 3.2-STABLE machine hasn't
> > > been able to stay up for much more then 24hrs before grinding to a halt.
> > > I've been working with Matt Dillon to resolve this, and we've got it
> > > narrowed down to INN's 'footprint', with his suggestion being:
> > >
> > > nnrpd should not be getting that big. There is an INN configuration
> > > parameter, I forget exactly what it is called... which causes nnrpd to
> > > load the hash table for the history file into memory after a certain
> > > number of message-id lookups. Find it, turn it off, and recompile --
> > > so nnrpd *never* tries to load the hash table into memory. This may
> > > solve your problem simply by reducing the size of nnrpd's footprint.
> > >
> > > The thing is, I don't know of any parameter that allows, or disallows
> > > this, and suspect it might be something from an older one? Or I'm just
> > > blind? Is this an option we still have in 2.3?
> > >
> > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
> > > Systems Administrator @ hub.org
> > > primary: scrappy at hub.org secondary: scrappy@{freebsd|postgresql}.org
> > >
> > >
> > >
> >
>
> Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
> Systems Administrator @ hub.org
> primary: scrappy at hub.org secondary: scrappy@{freebsd|postgresql}.org
>
>
>
More information about the inn-workers
mailing list