egghelp/eggheads community

socket

2003-05-12T04:43:01-04:00

Aditionaly, try using eggdrops dns functions to resolve the IP before making a connection.

It may possibly be that Tcl is failing to resolve.

Statistics: Posted by ppslim — Mon May 12, 2003 4:43 am

socket

2003-05-12T03:49:06-04:00

Guess I have to test it on other (faster) pc.

Statistics: Posted by caesar — Mon May 12, 2003 3:49 am

socket

2003-05-12T03:41:44-04:00

This sounds weird...if you don't get a reply from the host you're connecting to the connection should time out within less than a minute (the minimum time it would take your bot to ping timeout)

Try using -async when creating the socket, fconfigure it -blocking 0 and set up a fileevent $bla writable ... dealing with checking the connection. This way there should be no ping timeout no matter how [censored] up your system is

here's an alternative method of using catch to figure out if there's an error or not when opening the socket:
if {[catch {socket ...} bla]} {failed...$bla is the error msg} {connected...$bla is the socket id}

Statistics: Posted by user — Mon May 12, 2003 3:41 am

socket

2003-05-12T01:45:02-04:00

Code:

bind dcc n| sock dcc:sockproc dcc:sock {hand idx text} {  if {[llength $text] < 2} {    putdcc $idx "Usage: sock  "    return  }  set host [lindex $text 0]  set port [lindex $text 1]  catch {socket $host $port} bla  if {[string match "sock*" $bla]} {    putdcc $idx "connection established."    return  }  putdcc $idx "$bla"}

when I run an *test* he pings timed out. My local (lan) tests where ok, the internet ones he dies (ping timedout or something). Also I have tryed using the connect but I haven't understood exactly how to *control* it. I haven't got an successful thing with it, duno why. An example or something will be nice.

Statistics: Posted by caesar — Mon May 12, 2003 1:45 am