Aaron Bannert wrote:
>
> Ooh, that's a tough one. On the one hand, setters and getters for
> uid/gid won't really be portable to systems that don't have the concept
> of uid/gid. OTOH, I don't see any better way to do it (and I don't
> like the idea of global vars).
>
Hmmm. How about something l
On Sat, Sep 21, 2002 at 11:32:30AM -0700, Justin Erenkrantz wrote:
> On Sat, Sep 21, 2002 at 02:23:38PM -0400, Jim Jagielski wrote:
> > How would people say would be the best way to port the ShmemUIDisUser
> > code from 1.3 to 2.0/APR... Should I use a simple global var or wrap
> > that in some sor
On Sat, Sep 21, 2002 at 02:23:38PM -0400, Jim Jagielski wrote:
> How would people say would be the best way to port the ShmemUIDisUser
> code from 1.3 to 2.0/APR... Should I use a simple global var or wrap
> that in some sort of apr_set_sysv_uid(...)/apr_get_sysv_uid() pair
> which allows the state
How would people say would be the best way to port the ShmemUIDisUser
code from 1.3 to 2.0/APR... Should I use a simple global var or wrap
that in some sort of apr_set_sysv_uid(...)/apr_get_sysv_uid() pair
which allows the state to be function oriented rather than variable
oriented. I'm leaning tow
