Re: sun4-solaris polluted installation
Hi there, On Sat, 6 Apr 2002, Slava Bizyayev wrote: a lot of mess in common perl libraries. What of that could affect the installation? All sorts of things, but I'm still puzzled. To my mind you do not yet have enough evidence to point to a particular part of the system. If your production system were not using Perl in any way I would suggest that you delete the entire Perl installation and rebuild it from scratch with 5.6.1. (Actually I prefer 5.7.2 but I hesitate to suggest it for production use even though it seems fine to me. :) If it were my machine that is what I would do, production or not, because you really need to be able to rely on your Perl installation and at the moment evidently you cannot. Of course there is a risk that something would break, so you might prefer to rename the old Perl installation rather than delete it. You should of course make sure that the same compiler which built Perl also built mod_perl, for preference also using the same C libraries. Have you tried to run Perl's own 'make test' suite? 73, Ged.
Re: sun4-solaris polluted installation
If you're doing a demo, then I'd advise against installing over the production distributions. Create your own perl and Apache's. Philippe Chiasson wrote a paper for either ApacheCon or PerlCon about managing multiple modperl developers. If I recall correctly, each developer had their own Perl and Apache's living in each user's home directory with a CVS checkout of the latest application code. Before they were rolled out in production, he could then test against his copy of the current production environment. John [EMAIL PROTECTED]
Re: sun4-solaris polluted installation
Hi there, On Fri, 5 Apr 2002, Slava Bizyayev wrote: Nice try. Unfortunately, helpless... Don't you see two instances of mod_perl in common perl libraries? That's just flowers... Are you sure you understood my message? I don't understand your reply but you seem to be a little frustrated. Running two instances of a mod_perl Apache does not necessarily require that you run the Apache nor mod_perl 'make install' twice (although you may wish to compile different Apache and/or mod_perl binaries). You just have to create a second configuration and start a second server. You can for example compile a mod_perl Apache in your home directory and run it without root permissions. You don't need to do anything at all to the system's Perl installation until you mean to run the mod_perl Apache in production, listening to port 80. In fact it's probably better if you don't. Did you get 'make test' to run ok before attempting 'make install'? 73, Ged.
Re: sun4-solaris polluted installation
Yes John, I would prefer never to stick with that prod too, indeed I have to. It's a business requirement in this case. The future contract depends on what the performance will be achieved on that sever. The customer does not care too much about the demo (made) on dev. They wish to measure the performance on prod exactly, using the real data. And, the customer is right (as always;-)... Thanks, Slava - Original Message - From: John D Groenveld [EMAIL PROTECTED] To: Slava Bizyayev [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, April 06, 2002 3:10 PM Subject: Re: sun4-solaris polluted installation If you're doing a demo, then I'd advise against installing over the production distributions. Create your own perl and Apache's. Philippe Chiasson wrote a paper for either ApacheCon or PerlCon about managing multiple modperl developers. If I recall correctly, each developer had their own Perl and Apache's living in each user's home directory with a CVS checkout of the latest application code. Before they were rolled out in production, he could then test against his copy of the current production environment. John [EMAIL PROTECTED]
Re: sun4-solaris polluted installation
Yes Ged, I always make test before make install. Even just make, when appropriate... The idea to make the independently installed mod_perl enabled Apache has failed on this machine several times (when the native sysadmin tried to do that). Now, I have to find out why it fails. I see the polluted file system and a lot of mess in common perl libraries. What of that could affect the installation? I would like to know. I see an odd behavior of the make install (what I've just never been seeing on my dev). It might be OK, or may be wrong. I'd like to know too. I'd like to obtain probably some extra ideas, what to check/care about in this situation... Is there anybody, who can understand what I'm writing about? Thanks, Slava - Original Message - From: Ged Haywood [EMAIL PROTECTED] To: Slava Bizyayev [EMAIL PROTECTED] Cc: mod_perl Mailing List [EMAIL PROTECTED] Sent: Saturday, April 06, 2002 4:12 PM Subject: Re: sun4-solaris polluted installation Hi there, On Fri, 5 Apr 2002, Slava Bizyayev wrote: Nice try. Unfortunately, helpless... Don't you see two instances of mod_perl in common perl libraries? That's just flowers... Are you sure you understood my message? I don't understand your reply but you seem to be a little frustrated. Running two instances of a mod_perl Apache does not necessarily require that you run the Apache nor mod_perl 'make install' twice (although you may wish to compile different Apache and/or mod_perl binaries). You just have to create a second configuration and start a second server. You can for example compile a mod_perl Apache in your home directory and run it without root permissions. You don't need to do anything at all to the system's Perl installation until you mean to run the mod_perl Apache in production, listening to port 80. In fact it's probably better if you don't. Did you get 'make test' to run ok before attempting 'make install'? 73, Ged.
sun4-solaris polluted installation
Hi everyone, I have to (re)install mod_perl enabled Apache on prod server, which is polluted with the several previous unsuccessful attempts to do the similar job. It is not my server, but I may sudo su, when sure that the main prod (which is running on pure Apache using perl CGI scripts) will remain working... Basically, I need to clean up the mess and to install a brand new mod_perl enabled dedicated Apache to use some of my handlers for the performance demonstration. Actually, I need somebody very experienced with the sun4-solaris environment to assist me carefully on this slippery road... # perl -V Summary of my perl5 (revision 5.0 version 6 subversion 1) configuration: Platform: osname=solaris, osvers=2.6, archname=sun4-solaris uname='sunos tensor.vnet.net 5.6 generic_105181-06 sun4u sparc sunw,ultra-1 ' config_args='-Dcc=gcc -de' hint=recommended, useposix=true, d_sigaction=define usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef useperlio=undef d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef Compiler: cc='gcc', ccflags ='-fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFS ET_BITS=64', optimize='-O', cppflags='-fno-strict-aliasing -I/usr/local/include' ccversion='', gccversion='2.95.3 20010315 (release)', gccosandvers='solaris2.6' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=4321 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=8, usemymalloc=y, prototype=define Linker and Libraries: ld='gcc', ldflags =' -L/usr/local/lib ' libpth=/usr/local/lib /usr/lib /usr/ccs/lib libs=-lsocket -lnsl -lgdbm -ldb -ldl -lm -lc perllibs=-lsocket -lnsl -ldl -lm -lc libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib' Characteristics of this binary (from libperl): Compile-time options: USE_LARGE_FILES Built under solaris Compiled at May 10 2001 06:56:03 INC: /usr/local/lib/perl5/5.6.1/sun4-solaris /usr/local/lib/perl5/5.6.1 /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris /usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl Libraries in initial conditions: # ls -l /usr/local/lib/perl5/5.6.1/sun4-solaris/ total 1166 drwxr-xr-x 3 root other 1024 Mar 12 19:50 Apache -r--r--r-- 1 root other 35434 May 1 2001 Apache.pm drwxr-xr-x 2 bin bin 512 Mar 12 19:36 B -r--r--r-- 1 bin bin16467 May 10 2001 B.pm drwxr-xr-x 2 root other512 Mar 12 19:50 Bundle -r--r--r-- 1 bin bin 603 May 10 2001 ByteLoader.pm drwxr-xr-x 2 bin bin 1024 Mar 12 19:36 CORE -r--r--r-- 1 bin bin 188975 May 10 2001 Config.pm -r--r--r-- 1 bin bin57760 May 10 2001 DB_File.pm drwxr-xr-x 2 bin bin 512 Mar 12 19:36 Data drwxr-xr-x 2 bin bin 512 Mar 12 19:36 Devel -r--r--r-- 1 bin bin27317 May 10 2001 DynaLoader.pm -r--r--r-- 1 bin bin 6953 May 10 2001 Errno.pm -r--r--r-- 1 bin bin 5216 May 10 2001 Fcntl.pm drwxr-xr-x 2 bin bin 512 Mar 12 19:36 File -r--r--r-- 1 bin bin 1930 May 10 2001 GDBM_File.pm drwxr-xr-x 3 bin bin 512 Mar 29 12:17 IO -r--r--r-- 1 root other742 Jul 23 1998 IO.pm drwxr-xr-x 2 bin bin 512 Mar 12 19:36 IPC -r--r--r-- 1 bin bin 2408 May 10 2001 NDBM_File.pm -r--r--r-- 1 bin bin 2651 May 10 2001 O.pm -r--r--r-- 1 bin bin 2406 May 10 2001 ODBM_File.pm -r--r--r-- 1 bin bin15195 May 10 2001 Opcode.pm -r--r--r-- 1 bin bin18796 May 10 2001 POSIX.pm -r--r--r-- 1 bin bin50095 May 10 2001 POSIX.pod -r--r--r-- 1 bin bin 2517 May 10 2001 SDBM_File.pm -r--r--r-- 1 bin bin16668 May 10 2001 Safe.pm -r--r--r-- 1 bin bin10564 May 10 2001 Socket.pm drwxr-xr-x 2 bin bin 512 Mar 12 19:36 Sys -r--r--r-- 1 bin bin 3619 May 10 2001 XSLoader.pm -r--r--r-- 1 bin bin 1432 May 10 2001 attrs.pm drwxr-xr-x 25 bin bin 512 Mar 12 19:50 auto -r--r--r-- 1 root other 3277 Mar 3 2000 cgi_to_mod_perl.pod -r--r--r-- 1 root other 1096 Jul 11 2001 mod_perl.pm -r--r--r-- 1 root other 27538 Nov 28 2000 mod_perl.pod -r--r--r-- 1 root other 2706 Feb 29 2000 mod_perl_cvs.pod -r--r--r-- 1 root other512 Mar 12 16:44 mod_perl_hooks.pm -r--r--r-- 1 root other
Re: sun4-solaris polluted installation
Hi there, On Fri, 5 Apr 2002, Slava Bizyayev wrote: I have to (re)install mod_perl enabled Apache on prod server, which is polluted with the several previous unsuccessful attempts [snip] Actually, I need somebody very experienced with the sun4-solaris environment to assist me carefully on this slippery road... It's not that difficult. You can build another Apache with mod_perl and run it on the same machine without having any effect at all on the existing server, which can continue to run as normal. All you have to do is to configure the new server to listen to a port other than port 80 (to which presumably your production server is currently listening) and you can play with your new server until you get it to do what it needs to do. The details are all in the Guide: http://perl.apache.org/guide and you might also want to have a look at the Eagle Book: Writing Apache Modules with Perl and C, ISBN 1-56592-567-X and/or the Cookbook http://www.modperlcookbook.org if you haven't already. 73, Ged. (PS: GY: OK?)
Re: sun4-solaris polluted installation
Nice try. Unfortunately, helpless... Don't you see two instances of mod_perl in common perl libraries? That's just flowers... When I try to make install, for example # make install Writing /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/Apache/Filter/.packli st Appending installation info to /usr/local/lib/perl5/5.6.1/sun4-solaris/perllocal.pod Funny? Not for me... Best regards, Slava - Original Message - From: Ged Haywood [EMAIL PROTECTED] To: Slava Bizyayev [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, April 05, 2002 3:51 PM Subject: Re: sun4-solaris polluted installation Hi there, On Fri, 5 Apr 2002, Slava Bizyayev wrote: I have to (re)install mod_perl enabled Apache on prod server, which is polluted with the several previous unsuccessful attempts [snip] Actually, I need somebody very experienced with the sun4-solaris environment to assist me carefully on this slippery road... It's not that difficult. You can build another Apache with mod_perl and run it on the same machine without having any effect at all on the existing server, which can continue to run as normal. All you have to do is to configure the new server to listen to a port other than port 80 (to which presumably your production server is currently listening) and you can play with your new server until you get it to do what it needs to do. The details are all in the Guide: http://perl.apache.org/guide and you might also want to have a look at the Eagle Book: Writing Apache Modules with Perl and C, ISBN 1-56592-567-X and/or the Cookbook http://www.modperlcookbook.org if you haven't already. 73, Ged. (PS: GY: OK?)
