Re: Problem with mod_ssl and Apache 1.3.1
Ralf S. Engelschall wrote: Ok, I make you an offer: Create a temporary rse account on your box which has around 15 MB free disk space available and I'll try to setup Apache on your box and debug the code on your specific platform. I'm sure it's a local platform problem, but we cannot find it without tracing the code. Drop me a note with the password and machine/account info into my private mail folder when you established this. No need, they eventually figured the Apache + mod_ssl + JRun stuff themselves. Needless to say, commpiling code isn't my area of expertise, and so being pressed into getting it all up and running an hour before the deadline didn't do much for my humour. They picked up where I left off and it's now working fine. Thanks for your help! ~ James H.G. Redekop | [EMAIL PROTECTED] Web Programmer | http://www.residents.com/ The Residents UUNET Canada | http://www.residents.com/Goons/The Goon Show [EMAIL PROTECTED] | http://www.residents.com/Tzoq/ Home Page __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Problem with mod_ssl and Apache 1.3.1
James H.G. Redekop wrote: Ralf S. Engelschall wrote: I've compared his config file with the default config. Just harmless path differences. And his config file runs fine (after changing the paths, of course) for my with Apache 1.3.2 + mod_ssl 1.3.2. Seems I've now even to build with JRun to find the problem, perhaps it's related to it, who knows... When it's not JRun it's his platform. But here we have: Solaris 2.6 with GCC. Same as my webserver www.engelschall.com runs... H.. strange. Very, and frustrating. IBM is our customer on this one, and they are *not* happy with us because mod_ssl is not working. This is a real problem for us, and may cost us the customer and all that income -- over $2000/month. Unfortunately, Apache-SSL is not even *compiling*, on top of that. Normally, I try to stay silent unless there is something positive I can add to a thread, but in this case, I think things have gone too far... *I* believe that the user takes ALL responsibility for getting free and open source software working. I also believe that this is the nature of free software. Others have already said that it does work and are trying to help. It is inappropriate for anyone to try to make Ralf feel guilty or in any way responsible for their inability to make this software work. Ralf S. Engelschall wrote: Ok, I make you an offer: Create a temporary rse account on your box which has around 15 MB free disk space available and I'll try to setup Apache on your box and debug the code on your specific platform. I'm sure it's a local platform problem, but we cannot find it without tracing the code. Drop me a note with the password and machine/account info into my private mail folder when you established this. Wow! Ralf, I am now doubly impressed by your generosity (your software contribution, and now your remote, but "hands on" consulting services). I hope they understand and appreciate this extraordinary situation. -- Robert __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Problem with mod_ssl and Apache 1.3.1
In article you wrote: [...] *I* believe that the user takes ALL responsibility for getting free and open source software working. I also believe that this is the nature of free software. Others have already said that it does work and are trying to help. It is inappropriate for anyone to try to make Ralf feel guilty or in any way responsible for their inability to make this software work. Yes. But as long as people don't get really impertinent it's acceptable, at least to me. I know how frustrating it is when other people have a piece of software running but it will not run on my local environment for some strange reasons I cannot figure out myself. Then I'm happy when someone can help me. That's why I personally had no big problem this time (at least after ignoring the $$ part of the message, of course). Ok, I make you an offer: Create a temporary rse account on your box which has around 15 MB free disk space available and I'll try to setup Apache on your box and debug the code on your specific platform. I'm sure it's a local platform problem, but we cannot find it without tracing the code. Drop me a note with the password and machine/account info into my private mail folder when you established this. Wow! Ralf, I am now doubly impressed by your generosity (your software contribution, and now your remote, but "hands on" consulting services). I hope they understand and appreciate this extraordinary situation. Extraordinary software packages require extraordinary approaches, of course. But yes, I at least really hope people understand this privilege... BTW: For another mod_ssl user on this list I'm already doing remote consulting these hours. So it's nothing really unusual... ;-) Greetings, Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Problem with mod_ssl and Apache 1.3.1
In article you wrote: Ralf S. Engelschall wrote: Ok, I make you an offer: Create a temporary rse account on your box which has around 15 MB free disk space available and I'll try to setup Apache on your box and debug the code on your specific platform. I'm sure it's a local platform problem, but we cannot find it without tracing the code. Drop me a note with the password and machine/account info into my private mail folder when you established this. No need, they eventually figured the Apache + mod_ssl + JRun stuff themselves. Oh, fine. Needless to say, commpiling code isn't my area of expertise, and so being pressed into getting it all up and running an hour before the deadline didn't do much for my humour. They picked up where I left off and it's now working fine. Thanks for your help! Good to hear that they finally solved the problems. But perhaps you at least can ask them what the problem was and how they solved it? Because perhaps it was a subtle pitfall others can fall into in the future, too. Then we can add it to the INSTALL file or the FAQ section in the manual... Please always try to share experiences. Thanks. Greetings, Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
