Re: apache13 to apache13-modssl port migration

2003-09-15 Thread Dirk Meyer

I wrote:
  
  The transition is easy.
  
  1) deinstall all your ports(modules) depended on apache13
  2) install apache13-modssl.
  3) recompile all ports(modules)
  
  You can use apache13-modssl just as a replacment to apache13.
  But apache13-modssl uses extrand API, so you have to
  recompile all apache modules with apache13-modssl installed.
  
  all modules will build, install and run fine, maybe portupgrade
  will see wrong dependencys.
  
  some ports suports this very well using in /etc/make.conf
  APACHE_PORT=www/apache13-modssl
  
  still some ports use a obsolete setting like:
  APACHE_PORT=${PORTSDIR}/www/apache13-modssl
  AP_PORT=www/apache13-modssl
  AP_PORT=apache13-modssl
  
  This might be improved after The 4.9 Release
  http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/32604

cully wrote:

 Would you avoid portupgrade for this?
 
 I am a little shaky in the knees at this prospect.  This is on a 
 production web server getting over 1 million page views per day.  I use 
 mod_php4, mod_auth_pgsql, mod_gzip, mailman, and I have some other ports 
 installed like squirrelmail, mnogosearch, a bunch of pear libraries (not 
 even sure if they are dependent on apache13), phpMyAdmin and probably a 
 few other things I haven't even thought of. gulp
 
 Once this is done do all these ports change to think they are dependent 
 on apache13-modssl rather than www/apache13?

Yes, the PR#32604 will fix this.

But even now, you don't have to worry,
just be sure the modules are compiled with only www/apache13-modssl
installed, if portupgrade dones not overwrite with with www/apache13
in some coases you are perfectly fine, even if some ports register
a wrong dependency.

kind regards Dirk

- Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany
- [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: apache13 to apache13-modssl port migration

2003-09-11 Thread Lewis Watson
 culley harrelson wrote:
  I am a little shaky in the knees at this prospect.  This is on a
  production web server getting over 1 million page views per day.  I
use
  mod_php4, mod_auth_pgsql, mod_gzip, mailman, and I have some other
ports
  installed like squirrelmail, mnogosearch, a bunch of pear libraries
(not
  even sure if they are dependent on apache13), phpMyAdmin and probably
a
  few other things I haven't even thought of. gulp

 You have complete backups, right?  You probably should have a test
server where
 you can test the software upgrade under non-production conditions...


If you have another machine you can do this with much less stress.
1.Build the second machine (aka new server);
2. Rsync the files over (or from a backup).
3. Pull the network plug on the original;
4. Run a script to fire off any extra ip addresses for your new server.
5. Apachectl startssl on the new server.

Now it should be running and you can do spot checks to see how your
crucial sites are doing... If everything is ok thats great! If not then
pull the network plug on the new server and plug the old one back in
while you see where the problems are on the new one...
HTH,
Lewis




___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: apache13 to apache13-modssl port migration

2003-09-10 Thread Peter Elsner
I made the same transition...  I had apache13 installed from ports,
and then found myself in need of SSL support.
I didn't uninstall apache13, I simply went to the apache13-modssl port
and typed: make all install clean
No problems.  There was a new httpsd.conf file under my /usr/local/etc/apache
directory and I simply cut and pasted the virtual host information from
my httpd.conf to httpsd.conf file.  Then I followed the instructions on the
mod-ssl web site. http://www.modssl.org/
Good luck

Peter Elsner



At 08:04 PM 9/9/2003 -0700, you wrote:
I am currently running /usr/ports/www/apache13 and I want to switch to 
/usr/ports/www/apache13-modssl.  Has anyone make this transition?  I don't 
know what to expect and I don't have a freebsd test box right now.  I am 
worried about the ports dependent on apache13-- what happens to them if I 
just install apache13-modssl on top?  I do use portupgrade.

culley

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Peter Elsner [EMAIL PROTECTED]
Vice President Of Customer Service (And System Administrator)
1835 S. Carrier Parkway
Grand Prairie, Texas 75051
(972) 263-2080 - Voice
(972) 263-2082 - Fax
(972) 489-4838 - Cell Phone
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: apache13 to apache13-modssl port migration

2003-09-10 Thread culley harrelson



The transition is easy.

1) deinstall all your ports(modules) depended on apache13
2) install apache13-modssl.
3) recompile all ports(modules)
You can use apache13-modssl just as a replacment to apache13.
But apache13-modssl uses extrand API, so you have to
recompile all apache modules with apache13-modssl installed.
all modules will build, install and run fine, maybe portupgrade
will see wrong dependencys.
some ports suports this very well using in /etc/make.conf
APACHE_PORT=www/apache13-modssl
still some ports use a obsolete setting like:
APACHE_PORT=${PORTSDIR}/www/apache13-modssl
AP_PORT=www/apache13-modssl
AP_PORT=apache13-modssl
This might be improved after The 4.9 Release
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/32604
kind regards Dirk


Would you avoid portupgrade for this?

I am a little shaky in the knees at this prospect.  This is on a 
production web server getting over 1 million page views per day.  I use 
mod_php4, mod_auth_pgsql, mod_gzip, mailman, and I have some other ports 
installed like squirrelmail, mnogosearch, a bunch of pear libraries (not 
even sure if they are dependent on apache13), phpMyAdmin and probably a 
few other things I haven't even thought of. gulp

Once this is done do all these ports change to think they are dependent 
on apache13-modssl rather than www/apache13?

culley





___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: apache13 to apache13-modssl port migration

2003-09-10 Thread culley harrelson

You have complete backups, right?  You probably should have a test 
server where you can test the software upgrade under non-production 
conditions...

Yes of course.  I am 1/2 way through a 4 month stint on the road and all 
I have is a laptop...

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


apache13 to apache13-modssl port migration

2003-09-09 Thread culley harrelson
I am currently running /usr/ports/www/apache13 and I want to switch to 
/usr/ports/www/apache13-modssl.  Has anyone make this transition?  I 
don't know what to expect and I don't have a freebsd test box right now. 
 I am worried about the ports dependent on apache13-- what happens to 
them if I just install apache13-modssl on top?  I do use portupgrade.

culley

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: apache13 to apache13-modssl port migration

2003-09-09 Thread Mike Maltese
Don't install it on top of you old installation.

cd /usr/ports/www/apache13
make deinstall
 - or -
pkg_delete -f apache-1.3.xx

Then:
cd /usr/ports/www/apache13-modssl
make install clean
make certificate (optional)

Your original httpd.conf won't be deleted. You can use the new one
(httpd.conf-dist) as a reference for the SSL directives and migrate your
settings. You should also manually replace the old startup script with the
new one (apache.sh-sample) as it is slightly different (it enables mod_ssl
at startup).

 I am currently running /usr/ports/www/apache13 and I want to switch to
 /usr/ports/www/apache13-modssl.  Has anyone make this transition?  I
 don't know what to expect and I don't have a freebsd test box right now.
   I am worried about the ports dependent on apache13-- what happens to
 them if I just install apache13-modssl on top?  I do use portupgrade.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]