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?
So, on a Solaris 10 10/09 zone, I am seeing all resident memory being used up.
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special requirement, the access to the variables should be as quick as posible, which means that variables should be
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.
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).
I have a scenario where a server process needs to synchronize its access to shared memory segments with hundreds of client processes.
In my Ubuntu deployment script I have writen a function to secure shared memory. For a webserver it's important to secure the shared memory to tighten up security. Below you can find the code:
echo "tmpfs /dev/shm tmpfs tdefaults,noexec,nosuid 0 0" >> /etc/fstab
When I reboot the webserver it gets stuck. I can't see where it goes wrong. Do you have an idea, please let me know.
If I was to receive UDP packets on Linux (and I didn't mind changing some of the source code) what would be the fastest way for my application to read the packets?
Would I want to modify the network stack so that once a UDP packet is received it is written to shared memory and have the application access that memory?
This is a very basic question. The parent process will create some shared memory where it will put two integers in there, then it forked a child which will go to the shared memory and compute the sum of them. All this is fine, but how would the child inform the parent that it's done computing the sum? Do I need to create a pipe between the two processes to do this?