stas 2003/12/11 10:06:38 Modified: src/docs/2.0/user/porting compat.pod Log: temp solution for uid/gid calls Revision Changes Path 1.26 +26 -0 modperl-docs/src/docs/2.0/user/porting/compat.pod Index: compat.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/porting/compat.pod,v retrieving revision 1.25 retrieving revision 1.26 diff -u -u -r1.25 -r1.26 --- compat.pod 19 Nov 2003 19:46:11 -0000 1.25 +++ compat.pod 11 Dec 2003 18:06:38 -0000 1.26 @@ -679,7 +679,33 @@ See the C<L<APR::Pool|docs::2.0::api::APR::Pool>> manpage. +=head2 C<$s-E<gt>uid> +See the next entry. + +=head2 C<$s-E<gt>gid> + +apache-1.3 had server_rec records for server_uid and +server_gid. httpd-2.0 doesn't have them, because in httpd-2.0 the +directives User and Group are platform specific. And only UNIX +supports it: http://httpd.apache.org/docs-2.0/mod/mpm_common.html#user + +It's possible to emulate mod_perl 1.0 API doing: + + sub Apache::Server::uid { $< } + sub Apache::Server::gid { $( } + +but the problem is that if the server is started as I<root>, but its +child processes are run under a different username, e.g. I<nobody>, at +the startup the above function will report the C<uid> and C<gid> +values of I<root> and not I<nobody>, i.e. at startup it won't be +possible to know what the User and Group settings are in I<httpd.conf>. + +META: though we can probably access the parsed config tree and try to +fish these values from there. The real problem is that these values +won't be available on all platforms and therefore we should probably +not support them and let developers figure out how to code around it +(e.g. by using C<$E<lt>> and C<$(>). =head1 Request Object Methods
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
