Re: Incorrect memory sizes reported

hi, there! On Tue, 11 May 1999, Kevin Day wrote: > 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 SIZERES STATETIME WCPUCPU COMMAND > 139 root 2 0 257M

Re: Incorrect memory sizes reported

> > 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 S

RE: Incorrect memory sizes reported

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 SIZERES STATE

Incorrect memory sizes reported

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 SIZERES STATETIME WCPUCPU COMMAND 139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd 257M? :) ps sho