Yes, you either need a key or to pass the segment's ID. IPC_PRIVATE is meant to be used between two programs that can pass the ID, either because one forked the other and the ID is resident, or because they passed it in some other way. So, in IPC_PRIVATE world, you'd shmget in one and then pass the shmid to the other to shmat.
If you use the command "ipcs -m" you'll see all the shared memory segments. The KEY for IPC_PRIVATE (usually) is 0xffffffff, but you'll see a bunch of them. Each time you run this program you'll be creating another one. The ID for each will be different. Ultimately, it's the ID that determines which segment you attach to.
Think of shmget as a way to both create and lookup that ID. If you don't pass the same ID to each shmat call, you won't be looking at the same segment. Make sense?
Also, you probably mean sizeof(buffer) not sizeof(buffer[1]). The first will insure the segment can store the whole array, your way provides the segment only enough space to hold one element. Of course, this will cause an overflow.
edit: P.S. since you're never asking the shared memory segment be removed, it'll linger forever. You'll want to use ipcrm to get rid of it. Of course, you could also shmctl with the IPC_RMID command to ask it be removed. It'll hang around until all applications currently attached to it have detached. The kernel will detach the application when it is killed as well, so while it's good practice to shmdt, if you application dies in the middle the kernel will do it. Of course, on some O/Ses I've seen that fail and segments get "stuck" and the dumb machine needs a reboot to clean them up, lol.
thanks a lot for your exhaustive answer, i will try soon
---------- Post updated at 05:06 PM ---------- Previous update was at 04:26 PM ----------
so, for example i have to declare :
and then use that for shmget in both programs?
Dear Reader,
Is is necessary to attach / dettach the shared memory segments for write operations , if more than one program is accessing same shared memory segments..
I have used semaphore mutex and still I'm getting segmentation fault when I write to the segment when other program is already... (1 Reply)
I am running HP-UX B.11.11.
I'm increasing a parameter for a database engine so that it uses more memory to buffer the disk drive (to speed up performance). I have over 5GB of memory not being used.
But when I try to start the DB with the increased buffer parameter I get told.
"Not... (1 Reply)
Hi all :confused: ,
I am new to unix.I have been asked to implement shared memory in user's mode.What does this mean?What is the difference it makes in kernel mode and in users mode?What are the advantages of this impemenation(user's mode)?
And also i would like to know why exactly shared... (0 Replies)
what i want to do is have an int that can been written into by 2 processes but my code doesn't seem to work.
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/sem.h>
#include <sys/shm.h>
#include<stdio.h>
#define KEY1 (1492)
int main()
{
int shmid;
volatile int * addr;... (6 Replies)
hi,
this is the problem: i want to swap a linked list between 4 processes (unrelated), is there any way i can do that just by sending a pointer to a structure?
//example
typedef struct node
{
int x;
char c;
struct node *next;
} node;
or i should send the items ( x,c ) by... (9 Replies)
I need to create a shared library to access an in memory DB. The DB is not huge, but big enough to make it cumbersome to carry around in every single process using the shared library. Luckily, it is pretty static information, so I don't need to worry much about synchronizing the data between... (12 Replies)
I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability.
Obviously, I'll have to worry about mutual exclusion. (0 Replies)
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... (5 Replies)
Discussion started by: iamjag
5 Replies
LEARN ABOUT DEBIAN
ticker
NAME(1) General Commands Manual NAME(1)NAME
ticker - scroll messages across the screen
SYNOPSIS
ticker [options] [message]
DESCRIPTION
ticker is a program that continually scrolls a given message across the screen. There is also an interface to allow other programs to
change the message.
KEYS
+, [up arrow]
Increase scroll speed.
-, [down arrw]
Decrease scroll speed.
[space]
Pause. Press any key to unpause.
OPTIONS -h, --help
Show summary of options.
-u, --upper
Scroll text on the top line of the screen. (Default)
-l, --lower
Scroll text on the bottom line of the screen.
-fcolor, --foreground=color
Use the specified color as the forground color of the text that is scrolled. The colors that may be used are:
black gray
red brightred
green brightgreen
brown yellow
blue brightblue
magenta brightmagenta
cyan brightcyan
lightgray white
-bcolor, --background=color
Use the specified color as the background color of the text that is scrolled. On most terminals, the background color can only be
one of the colors listed in the first column above.
-dsecs, --delay=secs
Number of seconds delay between updates of the display. This controls how fast the text scrolls. You may use decimals to specify
faster scroll speeds. The default delay is 1 second; I find 0.1 more pleasing.
-snum, --sysv=num
Read messages to display from the sysv shared memory segment with an id of num. This is only for use by other programs that need to
be able to change the text ticker displays.
-Snum, --size=num
Size of the shared memory segment to read, when using shared memory communication with another program. Default is 80 characters.
-csecs, --check=secs
Minimum time between checks of the shared memory segment for a new message. Default is every second. It may in fact check consider-
ably less often, as it only checks for a new message once per time that the current message scrolls around the screen.
message
The message to scroll. Required unless -s is used, in which case it is optional.
NOTES
To use the other 23 or so lines of your screen for something useful while the ticker is running, you might want to use splitvt(1)AUTHOR
Joey Hess <joey@kitenet.net>
NAME(1)