Sponsored Content
Full Discussion: mutexing with sysv calls
Top Forums Programming mutexing with sysv calls Post 302286145 by Corona688 on Tuesday 10th of February 2009 12:04:26 PM
Old 02-10-2009
A semaphore with a value of one will make a good mutex. The first process in gets to decrement the semaphore, every other process has to wait. And when its done it increments the semaphore, letting the next process decrement it and take over.

Some good examples of sysv semaphores here.
 

8 More Discussions You Might Find Interesting

1. IP Networking

Identification of data calls & voice calls

Is there any facility to filter/identify the data calls and voice calls coming throug modem? OR Can we get the data or voice calls information through a script(preferably C Kermit)? (0 Replies)
Discussion started by: pcsaji
0 Replies

2. UNIX Desktop Questions & Answers

Using system calls

Hi, I'm new to UNIX system calls. Can someone share your knowledge as to how exactly system calls should be executed? Can they be typed like commands such as mkdir on the terminal itself? Also, are there any websites which will show me an example of the output to expect when a system call like... (1 Reply)
Discussion started by: ilavenil
1 Replies

3. BSD

system calls

what is the functions and relationship between fork,exec,wait system calls as i am a beginer just want the fundamentals. (1 Reply)
Discussion started by: sangramdas
1 Replies

4. UNIX for Dummies Questions & Answers

About system calls.

Hi all, I am new here . I want to know about system call in detail. As system calls are also function .How system identifies it.:) (2 Replies)
Discussion started by: vishwasrao
2 Replies

5. Shell Programming and Scripting

c++ calls bash

hi, i'm a noob i have a quuestion: is possible to call and run the bash script by c++ program? if so, is it posible in grafic? specially Qt ? thanks (8 Replies)
Discussion started by: 3.14.TR
8 Replies

6. UNIX for Dummies Questions & Answers

system calls in C

Hello, how would i be able to call ps in C programming? thanks, ---------- Post updated at 01:39 AM ---------- Previous update was at 01:31 AM ---------- here's the complete system call, ps -o pid -p %d, getpit() (2 Replies)
Discussion started by: l flipboi l
2 Replies

7. Solaris

SysV package creation, how to predefine DESTDIR

Hi Solaris experts How to predefine the DESTDIR in a Solaris package? Thanks (1 Reply)
Discussion started by: ./hari.sh
1 Replies

8. SCO

Trouble with sysv floppy images created under Linux

Hello, I wonder if anybody could help. I'm running SCO Xenix under Qemu on Xubuntu 16.04. I created a SYSV floppy image, but the files on it are poorly displayed when I mounted it under Xenix. I tried to create and format this image under Ubuntu as well as under Xenix. How could I create a... (6 Replies)
Discussion started by: Neelix
6 Replies
SHMCTL(2)						      BSD System Calls Manual							 SHMCTL(2)

NAME
shmctl -- shared memory control operations SYNOPSIS
#include <sys/types.h> #include <sys/ipc.h> #include <sys/msg.h> int shmctl(int shmid, int cmd, struct shmid_ds *buf); DESCRIPTION
The shmctl() system call performs some control operations on the shared memory area specified by shmid. Each shared memory segment has a data structure associated with it, parts of which may be altered by shmctl() and parts of which determine the actions of shmctl(). This structure is defined as follows in <sys/shm.h>: struct shmid_ds { struct ipc_perm shm_perm; /* operation permissions */ int shm_segsz; /* size of segment in bytes */ pid_t shm_lpid; /* pid of last shm op */ pid_t shm_cpid; /* pid of creator */ short shm_nattch; /* # of current attaches */ time_t shm_atime; /* last shmat() time*/ time_t shm_dtime; /* last shmdt() time */ time_t shm_ctime; /* last change by shmctl() */ void *shm_internal; /* sysv stupidity */ }; The ipc_perm structure used inside the shmid_ds structure is defined in <sys/ipc.h> and looks like this: struct ipc_perm { ushort cuid; /* creator user id */ ushort cgid; /* creator group id */ ushort uid; /* user id */ ushort gid; /* group id */ ushort mode; /* r/w permission (see chmod(2)) */ ushort seq; /* sequence # (to generate unique msg/sem/shm id) */ key_t key; /* user specified msg/sem/shm key */ }; The operation to be performed by shmctl() is specified in cmd and is one of: IPC_STAT Gather information about the shared memory segment and place it in the structure pointed to by buf. IPC_SET Set the value of the shm_perm.uid, shm_perm.gid and shm_perm.mode fields in the structure associated with shmid. The values are taken from the corresponding fields in the structure pointed to by buf. This operation can only be executed by the super-user, or a process that has an effective user id equal to either shm_perm.cuid or shm_perm.uid in the data structure associated with the shared memory segment. IPC_RMID Remove the shared memory segment specified by shmid and destroy the data associated with it. Only the super-user or a process with an effective uid equal to the shm_perm.cuid or shm_perm.uid values in the data structure associated with the queue can do this. The read and write permissions on a shared memory identifier are determined by the shm_perm.mode field in the same way as is done with files (see chmod(2) ), but the effective uid can match either the shm_perm.cuid field or the shm_perm.uid field, and the effective gid can match either shm_perm.cgid or shm_perm.gid. RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, -1 is returned and the global variable errno is set to indicate the error. ERRORS
shmctl() will fail if: [EPERM] cmd is equal to IPC_SET or IPC_RMID and the caller is not the super-user, nor does the effective uid match either the shm_perm.uid or shm_perm.cuid fields of the data structure associated with the shared memory segment. An attempt is made to increase the value of shm_qbytes through IPC_SET but the caller is not the super-user. [EACCES] The command is IPC_STAT and the caller has no read permission for this shared memory segment. [EINVAL] shmid is not a valid shared memory segment identifier. cmd is not a valid command. [EFAULT] buf specifies an invalid address. SEE ALSO
shmat(2), shmdt(2), shmget(2) BSD
August 17, 1995 BSD
All times are GMT -4. The time now is 01:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy