Hi,
David Gardiner wrote:
> The reason I noticed it was because my used disk space jump up to 100%
> and I started looking for what using it. du in the root directory gave
>
> [EMAIL PROTECTED]:/# du -hs *
Try "du -x / | sort -g | less".
bye, Roman
Hi,
David Gardiner wrote:
> The reason I noticed it was because my used disk space jump up to 100%
> and I started looking for what using it. du in the root directory gave
>
> root@munchkin:/# du -hs *
Try "du -x / | sort -g | less".
bye, Roman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
On Wed, 2002-10-16 at 14:24, David Gardiner wrote:
> Thanks Andrew, Olaf and Scott for your quick replys,
>
> The reason I noticed it was because my used disk space jump up to 100%
> and I started looking for what using it. du in the root directory gave
>
> [EMAIL PROTECTED]:/# du -hs *
> 2.6M
On Wed, 2002-10-16 at 14:24, David Gardiner wrote:
> Thanks Andrew, Olaf and Scott for your quick replys,
>
> The reason I noticed it was because my used disk space jump up to 100%
> and I started looking for what using it. du in the root directory gave
>
> root@munchkin:/# du -hs *
> 2.6Mb
In linux.debian.laptop, you wrote:
> ps: I have 256 M of ram and 320M is around the sum of my ram and the
> swap space thats being used so I assume it's the combined total of
> memory that the kernel is using. So I probably don't want to get rid of
> it do I :) just of my root partition if it wa
In linux.debian.laptop, you wrote:
> ps: I have 256 M of ram and 320M is around the sum of my ram and the
> swap space thats being used so I assume it's the combined total of
> memory that the kernel is using. So I probably don't want to get rid of
> it do I :) just of my root partition if it w
David Gardiner <[EMAIL PROTECTED]> writes:
> The reason I noticed it was because my used disk space jump up to 100%
> and I started looking for what using it. du in the root directory gave
>
> [snip command output]
>
> So if I trust du, df and ls in the /proc (which i probably shouldn't)
> direc
Thanks Andrew, Olaf and Scott for your quick replys,
The reason I noticed it was because my used disk space jump up to 100%
and I started looking for what using it. du in the root directory gave
[EMAIL PROTECTED]:/# du -hs *
2.6Mbin
2.9Mboot
4.0kcdrom
68k dev
9.4Metc
4.0k
David Gardiner <[EMAIL PROTECTED]> writes:
> what is /proc/kcore and why is it eating up my disk space?
> i.e.
> 262573 -r1 root root 268349440 Oct 16 08:59 kcore
> and a couple of minutes later
> 0 -r1 root root 320598016 Oct 16 09:03 kcore
> ^
On Wed, 16 Oct 2002 09:20:40 +1000
David Gardiner <[EMAIL PROTECTED]> wrote:
> what is /proc/kcore and why is it eating up my disk space?
It's not, it's a virtual file, it's actually the running kernel.
> i.e.
> 262573 -r1 root root 268349440 Oct 16 08:59 kcore
> and a co
David Gardiner <[EMAIL PROTECTED]> writes:
> The reason I noticed it was because my used disk space jump up to 100%
> and I started looking for what using it. du in the root directory gave
>
> [snip command output]
>
> So if I trust du, df and ls in the /proc (which i probably shouldn't)
> dire
what is /proc/kcore and why is it eating up my disk space?
i.e.
262573 -r1 root root 268349440 Oct 16 08:59 kcore
and a couple of minutes later
0 -r1 root root 320598016 Oct 16 09:03 kcore
^ ^
|
Thanks Andrew, Olaf and Scott for your quick replys,
The reason I noticed it was because my used disk space jump up to 100%
and I started looking for what using it. du in the root directory gave
root@munchkin:/# du -hs *
2.6Mbin
2.9Mboot
4.0kcdrom
68k dev
9.4Metc
4.0kflo
David Gardiner <[EMAIL PROTECTED]> writes:
> what is /proc/kcore and why is it eating up my disk space?
> i.e.
> 262573 -r1 root root 268349440 Oct 16 08:59 kcore
> and a couple of minutes later
> 0 -r1 root root 320598016 Oct 16 09:03 kcore
> ^
On Wed, 16 Oct 2002 09:20:40 +1000
David Gardiner <[EMAIL PROTECTED]> wrote:
> what is /proc/kcore and why is it eating up my disk space?
It's not, it's a virtual file, it's actually the running kernel.
> i.e.
> 262573 -r1 root root 268349440 Oct 16 08:59 kcore
> and a c
what is /proc/kcore and why is it eating up my disk space?
i.e.
262573 -r1 root root 268349440 Oct 16 08:59 kcore
and a couple of minutes later
0 -r1 root root 320598016 Oct 16 09:03 kcore
^ ^
|
16 matches
Mail list logo
