> Just as well. Some ancient X shm code I just looked at waits for a
> confirmation event back from X before doing IPC_RMID, so I guess this
> behaviour of not allowing shmat after IPC_RMID was already the case for
> a certain "SunOS" some years ago.
>
> As it should be.
I'd disagree. The remove and attach technique is very very commonly used
by other applications in order to ensure the segment is deleted if a program
crashed - directly analogous to open/unlink/read.
Gimp wont be the only thing that breaks. So the old behaviour needs to work
at least for SYS5 IPC, what posix ipc does is another matter
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 15 2000 - 21:00:21 EST