The man page for top defines SHR as:
t: SHR -- Shared Mem size (kb) The amount of shared memory used by a
task. It simply reflects memory that could be potentially shared with
other processes.
I can see this growing for one process but I am unsure of what exactly is being reported here.
Hello,
When creating shared memory in C, should be remove shared memory with shmctl function when don't need it. If it didn't remove, occupied shared memory stay and remain.
If we create shared memory repeatedly without removing unusable shared memory, /dev/shm will full.
Does Unix or Linux distributions do action to them?
My question is about setting the kernel shared memory for installing postgresql on mac osx 10.6.8. In the readme file of postgresql it is said:
Shared Memory
PostgreSQL uses shared memory extensively for caching and
inter-process communication.
I am building a Shared Library (.so) on Linux and I am compiling and linking in an object that is not dynamically linking in certain functions. These functions are "extern 'C'" functions. They are appearing in the normal symbol table of the shared object but not the external functions list or the dynamic functions list. I am compiling and linking using g++.
if you are interested in motivation Ill elaborate it in next few sentences, if not just skip to the Q.
I was thinking about making fast logger but the one that is not affected when program crashes(aka few last log msgs arent lost).
Through shmget and shmat, I am able to access the data stored in one program from another program.
I am making an rpm of my shared library. In the .spec file, I am writing the normal install commands in %install part ,making some soft links, running ldconfig on %post and %postun. I am not building library in rpm because I already have compiled and stripped library with me.
I was thinking of if there is any framework/library which provides a mechanism to test the functions which are not exported by the shared library.
I want to test working of functions listed in "t" section of shared library.
I am writing a C (shared) library. It started out as a single translation unit, in which I could define a couple of static global variables, to be hidden from external modules.
Now that the library has grown, I want to break the module into a couple of smaller source files.
Email this page
