06-08-2009
Um, rebooting and making "/proc going to normal again" is flawed reasoning and not sound advice technically. /proc appears to grow larger as your machine runs because it contains a representation of running applications memory (NOT DISK) space. So, rebooting makes /proc smaller because you're no longer running those applications. As soon as you start running applications again, /proc will grow as memory gets addressed. This is normal behavior!
>>> /proc has nothing whatsoever to do with disk space. <<<
Side note: don't reboot Unix machines arbitrarily, it makes Unix admins sad.
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
LEARN ABOUT OSX
tk_deleteclientmessagehandler
Tk_CreateClientMessageHandler(3) Tk Library Procedures Tk_CreateClientMessageHandler(3)
__________________________________________________________________________________________________________________________________________________
NAME
Tk_CreateClientMessageHandler, Tk_DeleteClientMessageHandler - associate procedure callback with ClientMessage type X events
SYNOPSIS
#include <tk.h>
Tk_CreateClientMessageHandler(proc)
Tk_DeleteClientMessageHandler(proc)
ARGUMENTS
Tk_ClientMessageProc *proc (in) Procedure to invoke whenever a ClientMessage X event occurs on any display.
_________________________________________________________________
DESCRIPTION
Tk_CreateClientMessageHandler arranges for proc to be invoked in the future whenever a ClientMessage X event occurs that is not handled by
WM_PROTOCOL. Tk_CreateClientMessageHandler is intended for use by applications which need to watch X ClientMessage events, such as drag
and drop applications.
The callback to proc will be made by Tk_HandleEvent; this mechanism only works in programs that dispatch events through Tk_HandleEvent (or
through other Tk procedures that call Tk_HandleEvent, such as Tk_DoOneEvent or Tk_MainLoop).
Proc should have arguments and result that match the type Tk_ClientMessageProc:
typedef int Tk_ClientMessageProc(
Tk_Window tkwin,
XEvent *eventPtr);
The tkwin parameter to proc is the Tk window which is associated with this event. EventPtr is a pointer to the X event.
Whenever an X ClientMessage event is processed by Tk_HandleEvent, the proc is called if it was not handled as a WM_PROTOCOL. The return
value from proc is normally 0. A non-zero return value indicates that the event is not to be handled further; that is, proc has done all
processing that is to be allowed for the event.
If there are multiple ClientMessage event handlers, each one is called for each event, in the order in which they were established.
Tk_DeleteClientMessageHandler may be called to delete a previously-created ClientMessage event handler: it deletes each handler it finds
that matches the proc argument. If no such handler exists, then Tk_DeleteClientMessageHandler returns without doing anything. Although Tk
supports it, it's probably a bad idea to have more than one callback with the same proc argument.
KEYWORDS
bind, callback, event, handler
Tk 8.4 Tk_CreateClientMessageHandler(3)