Well, i'd assume that it filled up the diskspace of the user $HOME that was running it. So, why not run 'du -m' on that user's $HOME?

On 11/26/02 18:56, Alan Jackson wrote:
I'm at my wit's end. A runaway vim process filled up my disk, and I can't
figure out *where*. I had cleared space a few days ago, and then it filled up
again, when I found and killed the gvim zombie. I get quite different
answers from different tools as well :

df tells me I've used 36 Gbytes, that is, the whole disk.
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hdb1             38464340  36316120    194316 100% /home

But when I try to find where it has gone with du,

du -k /home yields :

 5708312	.

 total kb, or 6 Gb. Where is the other 30?


--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                       	       [EMAIL PROTECTED]
Linux Step-by-step & TyGeMo: 		    http://netllama.ipfox.com

  7:00pm  up 45 days,  8:14,  3 users,  load average: 0.00, 0.04, 0.07

_______________________________________________
Linux-users mailing list
[EMAIL PROTECTED]
Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users

Reply via email to