On Mon, Feb 28, 2000 at 01:36:08PM -0800, Alfred Perlstein wrote:
> * Brooks Davis <[EMAIL PROTECTED]> [000228 13:23] wrote:
> > On a -current system as of a week or two ago (as well as a 3.3-RC and a
> > 2.2.8-STABLE box) I've found that mprotect fails with with EACCES when
> > trying to make a shared memory segment that was created user read/write
> > read-only. It works find if I malloc the memory instead and making the
> > shm segment write-only or inaccessible works fine as well. Is this
> > expected behavior? If so it's pretty weird.
>
> If you can point out any standards documents that mandate this
> behavior (i'm not saying there isn't any, but I'm unaware of it)
> or a list of OSs that support it, it would motivate action.
I've verified that it workes as expected on Solaris 2.6, Irix 6.4, and
some sort of RedHat with at 2.2.5-22 kernel (what I had immediate access
to). I can't quote a standards document though. The thing that really
got me was that I can take away all access, but I can't take away just
and exec write access. That's more then a little bizarre.
Thanks,
Brooks
--
Any statement of the form "X is the one, true Y" is FALSE.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
