Stas,
thanx a lot... in fact, I'm a quite newbie user of mod_perl and only subscribed to the list to ask this, thinking I might be doing something wrong... in fact, as noone answered, and I had subscribed with the address I use for [EMAIL PROTECTED], as the mod_perl messages were cluttering the folder, I just unsubscribed (so the copy of this mail to the list will probably bounce).
10 hours after I unsubscribed you sent your first answer, thankfully, you (and later Philippe) cc-ed me so I could stay in touch. I'm glad I was able to find a bug, and ever more glad that you were able to fix it.
The point is that I'm in the middle of the migration of the service (mail/web hosting/dns) farm for a large ISP (from windows to linux) and I have no time at all to try the new cvs version.
I've installed 1.99-12 in the web servers, and I'm in the process of final testing to go into production next week (we just missed tomorrow's deadline for going into production).
Anyway, I'm only using mod_perl to automatically generate a little over a thousand virtual hosts whose data (servername, serveraliases, path, etc.) is stored in an LDAP directory... and I think I'll live with this version until final 2.0 is out there.
If I'm able to find some spare time next weekend (not the one starting now), I'll try to check the cvs version.
Once again, thanx a lot.
I think it should work fine. So it'll be in mod_perl 1.99_13, when it gets released.
If having the 'httpd' name is significant you may want to apply this patch:
Index: src/modules/perl/modperl_config.c
===================================================================
RCS file: /home/cvs/modperl-2.0/src/modules/perl/modperl_config.c,v
retrieving revision 1.75
diff -u -r1.75 modperl_config.c
--- src/modules/perl/modperl_config.c 12 Feb 2004 02:05:28 -0000 1.75
+++ src/modules/perl/modperl_config.c 14 Feb 2004 01:37:09 -0000
@@ -178,8 +178,19 @@
#ifdef MP_USE_GTOP
scfg->gtop = modperl_gtop_new(p);
#endif
-
- modperl_config_srv_argv_push((char *)ap_server_argv0);
+
+ /* must copy ap_server_argv0, because otherwise any read/write of
+ * $0 corrupts process' argv[0] (visible with 'ps -ef' on most
+ * unices). This is due to the logic of calculating PL_origalen in
+ * perl_parse, which is later used in set_mg.c:Perl_magic_set() to
+ * truncate the argv[0] setting. remember that argv[0] passed to
+ * perl_parse() != process's real argv[0].
+ *
+ * as a copying side-effect, changing $0 now doesn't affect the
+ * way the process is seen from the outside.
+ */
+ modperl_config_srv_argv_push(apr_pstrmemdup(p, ap_server_argv0,
+ strlen(ap_server_argv0)));MP_TRACE_d(MP_FUNC, "new scfg: 0x%lx\n", (unsigned long)scfg);
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
