his weekend; deadlines and all that.
But this SM stuff is one of the things I need to have fixed, so I'm happy to
donate some time to help implement a flexible solution.
Thanks again.
Charlie
--
Charlie Garrison <[EMAIL PROTECTED]>
PO Box 141, Windsor, NSW 2756, Aust
iate your efforts
>> in finding and implementing a solution.
>
>Not a problem. It has been discussed in the past before, but passed over
>due to more important issues/bugs to resolve.
The ever-present 'more important issues'. I think we
in
finding and implementing a solution.
Thanks,
Charlie
--
Charlie Garrison <[EMAIL PROTECTED]>
PO Box 141, Windsor, NSW 2756, Australia
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-2
Good morning,
On 19/8/05 at 10:40 AM -0500, Jonathan Angliss <[EMAIL PROTECTED]> wrote:
>Hello Charlie Garrison,
>On Thursday, August 18, 2005, you wrote:
>
>> There is a 'frontend' apache server which proxies requests to a 'backend'
>> apach
with an
error message such as (port number changed to xxx):
Temporarily unable to connect to 202.51.168.70:xxx: Operation timed out
The xxx port number is the one used by the backend PHP server. How do I keep SM
from using that port number and just using port
with an
error message such as (port number changed to xxx):
Temporarily unable to connect to 202.51.168.70:xxx: Operation timed out
The xxx port number is the one used by the backend PHP server. How do I keep SM
from using that port number and just using port
