[SOLVED] Won't connect?

Suxen · Post by **Suxen** » Thu Feb 21, 2008 5:36 pm

Here's a great mystery that I seem entirely unable to solve. My configuration file is called run.eggdrop, just so I'd have something easy to remember.

From the command line:
# ./eggdrop run.eggdrop

It says:
Launched into the background

Yet I never see it connect and join the irc network and channel that it is set up to. However, if I use:
# ./eggdrop -n run.eggdrop

It connects to the network just fine! Why would this happen?

BeBoo · Post by **BeBoo** » Thu Feb 21, 2008 5:50 pm

Try telnetting to your bot after you run that first command and see if it's outputting anything or if you can even connect to it. Not sure what the -n flag is.

Brandon

Suxen · Post by **Suxen** » Thu Feb 21, 2008 6:02 pm

Can't telnet into it either for some reason.

-n stops it running in the background so everything is sent to the console instead

Post by **nml375** » Thu Feb 21, 2008 6:50 pm

You are having problems with threaded tcl-libraries not being properly detected as such, hence forking into background pretty much freezes the eggdrop.

Another reason for this kind of problems would be that there are multiple tcl-libraries installed on the system. However, with many recent linuxdistributions, this is an issue with libraries however.

A quickfix is to edit the config.h file after running ./configure, and defining the macro "HAVE_TCL_THREADS" to 1.

Suxen · Post by **Suxen** » Thu Feb 21, 2008 10:12 pm

Right on, thanks!! I felt like I was starting to go insane

For whatever reason, telnetting to the bot still doesn't seem to want to work even though the configuration is exactly as before, but I can live without it.

Alchera · Post by **Alchera** » Thu Feb 21, 2008 10:44 pm

Suxen wrote:For whatever reason, telnetting to the bot still doesn't seem to want to work even though the configuration is exactly as before, but I can live without it.

Try:

Code: Select all

/CTCP <nick> CHAT

Suxen · Post by **Suxen** » Thu Feb 21, 2008 10:49 pm

Can't seem to get a response from it that way either, which is why I defaulted to telnet (which used to work, before I went through recompiling everything). But it's still not the end of the world having to work without it.

Edit: Nevermind, the telnet mystery was that for some reason something else ended up taking up the port. Go figure. All is now good and well again