clar 2004/06/14 12:36:59
Modified: include apr_thread_proc.h
Log:
Fixed typo in API description
Revision Changes Path
1.108 +1 -1 apr/include/apr_thread_proc.h
Index: apr_thread_proc.h
===================================================================
RCS file: /home/cvs/apr/include/apr_thread_proc.h,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -r1.107 -r1.108
--- apr_thread_proc.h 14 Jun 2004 17:26:19 -0000 1.107
+++ apr_thread_proc.h 14 Jun 2004 19:36:58 -0000 1.108
@@ -518,7 +518,7 @@
* Determine if the child should start in its own address space or using the * current one from its parent
* @param attr The procattr we care about. - * @param addrspace Should the child start in ouw address space? Default is no. + * @param addrspace Should the child start in its own address space? Default is no.
default is yes everywhere but Netware...
what are the concerns with running child in same address space? if safer to run in separate address space, shouldn't that be the default?
*/
APR_DECLARE(apr_status_t) apr_procattr_addrspace_set(apr_procattr_t *attr,
apr_int32_t
addrspace);
