snoopy@sopwith.UUCP (Snoopy) (05/05/89)
In article <1868@blake.acs.washington.edu> mtsu@blake.acs.washington.edu (Montana State) writes: | This is a good point, but what I would like to know is why df needs so much | core to run in. While df is blowing up with not enough core, ps, top, and | lisp can all fire up and run. I did a ps on a df that was stuck waiting | for an NFS server, and it showed an size of 1034K of memory. What does | it need all of this space for?? 1034K ? That's over a megabyte to you and me! Mine is much smaller: PID TT STAT TIME SL RE PAGEIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND 29893 71 D N 0:00 0 1 3 32 3 xx 10 3 20.5 0.4 df Let me guess: ps, top and lisp don't deal with NFS, right? While df does because you have a bunch of filesystems mounted using NFS. Anything NFS touches swells up without bound. (NFS = Not Finitely Sized) _____ /_____\ Snoopy "DFS > NFS" /_______\ |___| tekecs.gwd.tek.com!sopwith!snoopy qiclab!sopwith!snoopy |___| sun!nosun!illian!sopwith!snoopy parsely!sopwith!snoopy