I see you just fixed it... it's weird cause I tested.. but
I think I know what's the issue.. it's the ::Socks5::Init..
it's called in 3 different places in proxy.tcl.. I 'catch'ed
2 of them, and missed the 3rd one..
I thought it would be best to catch the whole socks::init in
case there's an error
Youness Alaoui wrote:
> On Sun, Oct 26, 2008 at 02:21:00AM +0300, Vivia Nikolaidou wrote:
>>> Another one is SOCKS5 support. If you enable socks but the socks server
>>> isn't running (eg I set up an ssh tunnel and did my pass wrong and
>>> didn't notice) when opening aMSN the application fails
On Sun, Oct 26, 2008 at 02:21:00AM +0300, Vivia Nikolaidou wrote:
>
> > Another one is SOCKS5 support. If you enable socks but the socks server
> > isn't running (eg I set up an ssh tunnel and did my pass wrong and
> > didn't notice) when opening aMSN the application fails to launch with an
> >
> Another one is SOCKS5 support. If you enable socks but the socks server
> isn't running (eg I set up an ssh tunnel and did my pass wrong and
> didn't notice) when opening aMSN the application fails to launch with an
> error dumped to console.
What error? I can't reproduce this. Due to connec
