11-26-2001
The most probable cause is that someone did a "kill -9" to fbackup.
Another possibility is that your system is out of semaphores.
Type "ipcs -sp" and see how many semaphores you have. If this number is equal to the value semmns you are out of semaphores. You should increase the value of semmns and rebuild the kernel.
If the number of semaphores is less tham semmns then someone must have did the "kill -9" to a running fbackup process. It is possible to use ipcrm to remove the semaphore, but it's tough to know which one. A reboot will may be the safest bet. And remind people to lay off the "kill -9" command.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello evry body,
I search to do a extend from semaphore on a SunOS 5.5.1 . I know the /etc/system file but I don't know the code line to put in this file . Help me a find a solution for my computer .
Merci d'avance . (1 Reply)
Discussion started by: Romeo_91
1 Replies
2. UNIX for Dummies Questions & Answers
hi, is there any command where we can monitor semaphores? (1 Reply)
Discussion started by: yls177
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I'm new to UNIX.
I need to know what's a semaphore
Do reply.
Thanks
VJ (3 Replies)
Discussion started by: vjsony
3 Replies
4. Shell Programming and Scripting
Hi,
I am looking to use a semaphore for the first time in one of my scripts. I am just wondering if there are any simple examples or tutorials around?
I am a beginner so the simpler the better :)
Thanks
-Jaken (2 Replies)
Discussion started by: Jaken
2 Replies
5. UNIX for Dummies Questions & Answers
what is semaphore? can any body explain it in a more simple way than the manual ??
replies appreciated
Regards
raguram R (7 Replies)
Discussion started by: raguramtgr
7 Replies
6. Programming
In my server code there is a thread per client...
The server call accept() and after that start the thread.
So there is a thread for client that save in RAM the client's message, that will be send to other clients.
Now in RAM I have created a shared memory in which thread read and write(save)... (2 Replies)
Discussion started by: italian_boy
2 Replies
7. Shell Programming and Scripting
Control two exclusively shared resources(semaphore). The two resources are two files. The producer will write even numbers to one file, and odd numbers to another one. The consumer respectively reads from each file until it gets 5 even numbers and 5 odd numbers.
Can any one help me with the... (0 Replies)
Discussion started by: gokult
0 Replies
8. Programming
If I create a semaphore and then I fork a number of child processes then all the child process use that same semaphore.
Since the process address spaces are different rfom each other then how all the child process are able to access the same semaphore?
I understand that semaphore/mutex is at os... (0 Replies)
Discussion started by: rupeshkp728
0 Replies
9. Solaris
Can anyone tell me abt the Semaphore concept and what is semaphore???
is semaphore id is associated in terms as in resources like semaphore id 1 indicates cpu share unit is given and semaphore id 2 will indicate abt the memore or semaphore id 3 will tell us the i/o components (1 Reply)
Discussion started by: aarjun07
1 Replies
10. UNIX for Beginners Questions & Answers
I was asked to add this piece of code to a c program which I will execute through the shell:
for(long i = 0; i < NITER; i++)
{ sem_wait( &sema);
count++;
sem_post( &sema); }
I didn't get it, which is the critical section ? if it's "count++" how would a thread wake up in order to enter it... (1 Reply)
Discussion started by: uniran
1 Replies
SEM_GET(3) 1 SEM_GET(3)
sem_get - Get a semaphore id
SYNOPSIS
resource sem_get (int $key, [int $max_acquire = 1], [int $perm = 0666], [int $auto_release = 1])
DESCRIPTION
sem_get(3) returns an id that can be used to access the System V semaphore with the given $key.
A second call to sem_get(3) for the same key will return a different semaphore identifier, but both identifiers access the same underlying
semaphore.
PARAMETERS
o $key
-
o $max_acquire
- The number of processes that can acquire the semaphore simultaneously is set to $max_acquire.
o $perm
- The semaphore permissions. Actually this value is set only if the process finds it is the only process currently attached to the
semaphore.
o $auto_release
- Specifies if the semaphore should be automatically released on request shutdown.
RETURN VALUES
Returns a positive semaphore identifier on success, or FALSE on error.
CHANGELOG
+--------+-----------------------------------------+
|Version | |
| | |
| | Description |
| | |
+--------+-----------------------------------------+
| 4.3.0 | |
| | |
| | The $auto_release parameter was added. |
| | |
+--------+-----------------------------------------+
NOTES
Warning
When using sem_get(3) to access a semaphore created outside PHP, note that the semaphore must have been created as a set of 3 sema-
phores (for example, by specifying 3 as the nsems parameter when calling the C semget() function), otherwise PHP will be unable to
access the semaphore.
SEE ALSO
sem_acquire(3), sem_release(3), ftok(3).
PHP Documentation Group SEM_GET(3)