Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 May 1999 17:18:12 -0500 (CDT)
From:      Kevin Day <toasty@home.dragondata.com>
To:        davids@webmaster.com (David Schwartz)
Cc:        current@freebsd.org
Subject:   Re: Incorrect memory sizes reported
Message-ID:  <199905112218.RAA18856@home.dragondata.com>
In-Reply-To: <000101be9bfb$6fd43f70$021d85d1@whenever.youwant.to> from David Schwartz at "May 11, 1999  3:13: 2 pm"

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> 
> 	This is normal. It's using a lot of virtual memory. Fortunately, virtual
> memory is cheap.
> 
> 	DS
> 
> > I'm not sure if this is related to the bug I found in 3.1,
> > regarding mmaping
> > devices, then forking, but with my -current NFS server:
> >
> >   PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
> >   139 root       2   0   257M   452K select   0:00  0.00%  0.00% rpc.statd
> >
> > 257M? :) ps shows similar info...
> >
> >
> > Kevin
> 
> 

Ok, I stand corrected then.... 

I hadn't seen this before...

2.2.8:
root     14127  0.0  0.1   176  492  ??  Ss    5:14PM    0:00.00 rpc.statd

3.1:
root     853  0.0  0.7  172  416  ??  Ss    7:18AM   0:00.00 rpc.statd


There still is the issue I described a while back that would make children
show negative numbers in 'size' though, that i can confirm isn't sucking
that much VM.


Kevin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?199905112218.RAA18856>