Sponsored Content
Full Discussion: semaphores
Top Forums Programming semaphores Post 97328 by qntmteleporter on Saturday 28th of January 2006 07:10:33 PM
Old 01-28-2006
It sure is a wonderful documentation resource!

Thanks a ton!
 

10 More Discussions You Might Find Interesting

1. Programming

Semaphores

Dear Reader, I'm in a multiprocess environment working with shared mem and semaphores as mutex.. The problem is -- If one of the process hooked up with the semaphore and accessing the shared mem, terminates abruptly ( or got killed ), other process which are in want of the semaphore are... (1 Reply)
Discussion started by: joseph_shibu
1 Replies

2. UNIX for Dummies Questions & Answers

Semaphores

Hi all, I am using HP 10.20 on A 9000/785. My question is: If I am the only person logged in as root at the moment, how many "semaphore proccesses" should I have?? Is it only one, or it is relevant to other system proccesses? Here is what I get listing the current semaphores # ipcs -sp... (1 Reply)
Discussion started by: guest100
1 Replies

3. Shell Programming and Scripting

semaphores

Hi Friends, If i execute this command it comes back with 300 lines: ipcs|grep cerebrus >>> i would like to clear the semaphores but ipcrm can remove one id at a time. is there a quicker way of removing semaphores maybe using awk? Regards, (1 Reply)
Discussion started by: kekanap
1 Replies

4. Programming

semaphores using up and down

been searching around on how to use an up and down function with semaphores but i can't find an example. i looked into using: "semop" but i have no idea how to use it. I have been able to declared the semaphores using semget and initializing them using semctl. (7 Replies)
Discussion started by: ddx08
7 Replies

5. UNIX for Advanced & Expert Users

How many semaphores?

Hello, first of all I apologize if this thread is not in the correct section of this forum, but this one just seemed the most appropriate. The question I have does not concern Unix specifically, it applies to virtually any OS, however it is in Unix where I learned about this problem. So, the... (8 Replies)
Discussion started by: Watto86
8 Replies

6. Programming

Semaphores Urgent

Hello, Iam trying to implement the sleeping barber problem using semaphores and running on UNIX machine. Iam linking it to the thread libraries : bash-2.03$ g++ sleepingBarber.cpp -lpthread -o sleeping but when i execute it i get the following error: bash-2.03$ sleeping Starting Program... (4 Replies)
Discussion started by: mohit.choudhary
4 Replies

7. Programming

Problem with semaphores

Hello, I was doing an exercise of semaphores and shared memory, namely the barbers: -B number of barbers -S number of chairs -C number of customers. I have done already and I compiled the code, but when run I get an error segment. Can not be and it took several days. If anyone sees the error... (2 Replies)
Discussion started by: ciudadwifi
2 Replies

8. UNIX for Dummies Questions & Answers

semaphores

I am having problem with semaphores. I am trying to protect line where process prints so that every process with print in proper order.This is the code.. #include <stdio.h> #include <stdlib.h> #include <unistd.h> #include <sys/ipc.h> #include <sys/sem.h> #include <sys/types.h> union... (3 Replies)
Discussion started by: joker40
3 Replies

9. Programming

about Semaphores

Hello Everybody, I am building a server. this server contains some data. Clients may modify this data or read this data. If a client is reading the data and at the same time another client is modifying the data then at this case the reading client may read some false data (some old mixed with... (1 Reply)
Discussion started by: Omar_Mokhtar
1 Replies

10. Solaris

Semaphores

Hi, Can somebody please explain me what semaphores are? there purpose? and there effects? Thanks in advance:) (0 Replies)
Discussion started by: Laxxi
0 Replies
XKILL(1)						      General Commands Manual							  XKILL(1)

NAME
xkill - kill a client by its X resource SYNOPSIS
xkill [-display displayname] [-id resource] [-button number] [-frame] [-all] DESCRIPTION
Xkill is a utility for forcing the X server to close connections to clients. This program is very dangerous, but is useful for aborting programs that have displayed undesired windows on a user's screen. If no resource identifier is given with -id, xkill will display a spe- cial cursor as a prompt for the user to select a window to be killed. If a pointer button is pressed over a non-root window, the server will close its connection to the client that created the window. OPTIONS
-display displayname This option specifies the name of the X server to contact. -id resource This option specifies the X identifier for the resource whose creator is to be aborted. If no resource is specified, xkill will display a special cursor with which you should select a window to be kill. -button number This option specifies the number of pointer button that should be used in selecting a window to kill. If the word "any" is speci- fied, any button on the pointer may be used. By default, the first button in the pointer map (which is usually the leftmost but- ton) is used. -all This option indicates that all clients with top-level windows on the screen should be killed. Xkill will ask you to select the root window with each of the currently defined buttons to give you several chances to abort. Use of this option is highly discour- aged. -frame This option indicates that xkill should ignore the standard conventions for finding top-level client windows (which are typically nested inside a window manager window), and simply believe that you want to kill direct children of the root. CAVEATS
This command does not provide any warranty that the application whose connection to the X server is closed will abort nicely, or even abort at all. All this command does is to close the connection to the X server. Many existing applications do indeed abort when their connection to the X server is closed, but some can choose to continue. XDEFAULTS
Button Specifies a specific pointer button number or the word "any" to use when selecting windows. SEE ALSO
X(7), xwininfo(1), XKillClient and XGetPointerMapping in the Xlib Programmers Manual, KillClient in the X Protocol Specification AUTHOR
Jim Fulton, MIT X Consortium Dana Chee, Bellcore X Version 11 xkill 1.0.3 XKILL(1)
All times are GMT -4. The time now is 01:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy