06-10-2009
I guess that I will try one more time... /proc is an illusion. It does not actually consume disk space.
If you create a new process with, say pid 1234 and it is using 300 MB of memory, /proc/1234 will magicly pop into existence and it will be 300 MB in size. But you did not lose any disk space. Not one byte.
Now, kill pid 1234 and /proc/1234 will vanish. But you won't get back even one byte of disk space. /proc/1234 is just a way to treat a process as if it was a data file. This makes stuff like debuggers very easy to write.
/dev, on the other hand, is probably a real problem. It is usually caused by someone doing something like:
tar cvf /dev/wrong-name-for-tape-drive /big/collection/of/files
Maybe:
find /dev -type f
will find it for you.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I noticed that whenever something is printed from my workstation, the available disk space in the /dev/dsk/c0t0d0s0 decreases considerably. Hence, after using my workstation for sometime, I encounter an error message: "Filesystem Full" that prevents me from printing any further.
Is there a way to... (16 Replies)
Discussion started by: ilak1008
16 Replies
2. Programming
I wrote a wrapper (call it prog1) around another program (call it prog2) for security purposes. When prog1 launches prog2 it sets the argv value to be "prog1" so that "prog2" does not show up when you use the "ps" command. Howerver, if you use the option "-o fname" with "ps" then the file name for... (3 Replies)
Discussion started by: wilbur
3 Replies
3. Solaris
Hi,
I am working on SunOS perlrate 5.10 Generic_127111-09 sun4v sparc SUNW,SPARC-Enterprise-T5120.
The server has an LSISAS3801E HBA card installed and is connected to a StorageTek 2530 array.
I have made a volume on arrary using Common Array Manager.
I can see the volume on server:
... (2 Replies)
Discussion started by: seanban
2 Replies
4. Solaris
Good morning, sir!
I've a problem with FileSystem, the problem is FileSystem is full
First time, I've already read carefully the sticky thread
FileSystem full - What to lock for
https://www.unix.com/sun-solaris/25840-filesystem-full-what-look.html
And then, I will post some information of... (4 Replies)
Discussion started by: trantuananh24hg
4 Replies
5. UNIX for Dummies Questions & Answers
my root filesystem is eventually full "/dev/rdsk/c1d0s0" as a result i cannot boot to the operating system, i booted into the fail safe mode to check the space using df -h command i discover that it is eventually full. Also to my amazement i found that i cannot see the filesystem which mounted on... (1 Reply)
Discussion started by: seyiisq
1 Replies
6. Red Hat
Hi All,
How do I increase the root filesystem? It's getting full.
/ 90%
Here's the break down, below
232 dev
5624 tmp
*6764 bin
16860 root
*19680 sbin
*20436 lib64
28329 boot
*47992 etc
150012 var
*254540 lib
651708 home
*2445044 usr (5 Replies)
Discussion started by: itik
5 Replies
7. UNIX for Dummies Questions & Answers
Hello everybody, a very basic question.
Inspite of me deleting huge files in a filesystem(AIX 5.3) in oracle folder, the filesystem when i check using df -k still shows 100% full. Does that mean there is a process still pointing to the files which i deleted. how do i work around this.
Thanks!... (3 Replies)
Discussion started by: karthikosu
3 Replies
8. Linux
Hello,
I am having a nightmare with Tripwire on Linux..... I cannot get it to ignore the /proc filesystem, which I want to completely ignore for now
Has anyone here successfully configured Tripwire on Linux and completed ignored the /proc filesystem ?
If so, please reply and tell me how... (0 Replies)
Discussion started by: Neo
0 Replies
9. Solaris
In our shop we have to run a batch cycle. Every so often while we are running batch we get a filesystem full situation that causes batch to stop or slow down. Anyway, the practiced procedure is to look for large files and zip them. This takes a lot of time. We are in a sun solaris environment. What... (1 Reply)
Discussion started by: Harleyrci
1 Replies
BLOGD(8) The SuSE boot concept BLOGD(8)
NAME
blogd - boot logging on /dev/console
SYNOPSIS
/sbin/blogd [/dev/realtty]
DESCRIPTION
Without argument blogd determines the real underlying character device of /dev/console. blogd spawns a pty/tty pair to reconnect the cur-
rent /dev/console with the slave of the pty/tty pair. During writing information from this slave to the real character device a ring buffer
is used to hold the information for writing it to an existing logging file.
To fetch the real tty of /dev/console the program showconsole(8) can be used. This has the advantage that blogd will not hold the real
character device of /dev/console as its controlling tty (would hangup any running getty on that character device).
SIGNALS
blogd knows a few signal to contol its behavior.
SIGQUIT, SIGINT, and SIGTERM
will cause blogd tries to write out the ring buffer and to exit.
SIGIO says blogd that now it is able to write on /var/log/boot.msg which means that the file system is mounted read/write and the kernel
messages are written to that file.
SIGSYS says blogd that it should stop writing to disk but continue to repeat messages to the old devices of the system console.
BUGS
blogd needs a mounted /proc and /dev/pts file system and tries to set the controlling tty to stdin if the real character device of
/dev/console is not given. After reading /proc blogd tries to restore the status of the controlling tty to avoid problems with getty pro-
cesses. This can fail because blogd forks to run in the background as a daemon.
FILES
/proc/<pid of blogd>/stat
the stat file of the blogd process.
/dev/console
the system console.
/var/log/boot.msg
logging file which is created by klogd(8) or dmesg(8).
SEE ALSO
showconsole(8), syslogd(8), klogd(8), dmesg(8), proc(5).
COPYRIGHT
2000 Werner Fink, 2000 SuSE GmbH Nuernberg, Germany.
AUTHOR
Werner Fink <werner@suse.de>
3rd Berkeley Distribution Nov 10, 2000 BLOGD(8)