Disabling the uid/gid setting of SysV shared memory

[Jim Jagielski <ji...@jaguNET.com>]

I've been mulling over how to port the ShmemUIDisUser logic from 1.3
to 2.0, and keep on getting back to either an implementation that
is intrinsicly non-threadsafe (via a static or global state var)
or one that requires a change to the apr_shm_create argument list.
Neither one sits well. I'd prefer it staying runtime rather than
compile-time. Ideas?
-- 
===========================================================================
   Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
      "A society that will trade a little liberty for a little order
             will lose both and deserve neither" - T.Jefferson

Re: Disabling the uid/gid setting of SysV shared memory

[Thom May <th...@planetarytramp.net>]

* Cliff Woolley (jwoolley@virginia.edu) wrote :
> On Mon, 23 Sep 2002, Jim Jagielski wrote:
> 
> > is intrinsicly non-threadsafe (via a static or global state var)
> > or one that requires a change to the apr_shm_create argument list.
> > Neither one sits well. I'd prefer it staying runtime rather than
> > compile-time. Ideas?
> 
> How about apr_shm_create_ex()?  That would be consistent with many other
> things in APR, whereby there's a "simple version" that has some (possibly
> undesirable) default behavior, and an "extra args" version that gives the
> user-code more control.
Sounds good here. 
+1

-Thom

-- 
Thom May -> thom@planetarytramp.net

<aj> *sigh* you'd think a distribution composed of 6000
packages distributed across 13 different architectures (in various stages
between pre-alpha and release quality), maintained by 700 amateurs with often
conflicting goals who're globally distributed and have rarely met each other
-- you'd think a distribution like that would be simpler...

RE: Disabling the uid/gid setting of SysV shared memory

[Sander Striker <st...@apache.org>]

> From: Cliff Woolley [mailto:jwoolley@virginia.edu]
> Sent: 23 September 2002 15:58

> On Mon, 23 Sep 2002, Jim Jagielski wrote:
> 
> > is intrinsicly non-threadsafe (via a static or global state var)
> > or one that requires a change to the apr_shm_create argument list.
> > Neither one sits well. I'd prefer it staying runtime rather than
> > compile-time. Ideas?
> 
> How about apr_shm_create_ex()?  That would be consistent with many other
> things in APR, whereby there's a "simple version" that has some (possibly
> undesirable) default behavior, and an "extra args" version that gives the
> user-code more control.

+1.

Sander

Re: Disabling the uid/gid setting of SysV shared memory

[Cliff Woolley <jw...@virginia.edu>]

On Mon, 23 Sep 2002, Jim Jagielski wrote:

> is intrinsicly non-threadsafe (via a static or global state var)
> or one that requires a change to the apr_shm_create argument list.
> Neither one sits well. I'd prefer it staying runtime rather than
> compile-time. Ideas?

How about apr_shm_create_ex()?  That would be consistent with many other
things in APR, whereby there's a "simple version" that has some (possibly
undesirable) default behavior, and an "extra args" version that gives the
user-code more control.

--Cliff