bot shown running in shell but cant connect it

audi · Post by **audi** » Mon Jun 22, 2009 12:11 pm

When i log in into my shell and cd "bot" then i send command "./eggdrop 'bot', it say already connected.when i telnet the bot i cant connect to it.I did the following
1-i kill -9 'pid'
2-i retyped the above commands
3-it showed launched but i could not connect nor the bot get connected to irc.
can any one guide me am newbie in eggdrops.i also dont know how to get into through dcc.
Thanks in anticipation.

DaRkOoO · Post by **DaRkOoO** » Mon Jun 22, 2009 12:37 pm

try ./eggdrop -nm eggdrop.conf

audi · Post by **audi** » Mon Jun 22, 2009 1:17 pm

tnx for quick reply i did it and it gave following msg.
[17:10] --- Loading eggdrop v1.6.19 (Mon Jun 22 2009)
[17:10] * Please make sure you edit your config file completely.

i again gave command./eggdrop 'bot'
again the msg came.' i detect that bot running in the same directory.I again tried to telnet to bot but cudnt.Am quite new in eggdrops.Dont know how to edit config file editing.
Regards

speechles · Post by **speechles** » Mon Jun 22, 2009 6:08 pm

audi wrote:tnx for quick reply i did it and it gave following msg.
[17:10] --- Loading eggdrop v1.6.19 (Mon Jun 22 2009)
[17:10] * Please make sure you edit your config file completely.

i again gave command./eggdrop 'bot'
again the msg came.' i detect that bot running in the same directory.I again tried to telnet to bot but cudnt.Am quite new in eggdrops.Dont know how to edit config file editing.
Regards

The only way you would be seeing "[17:10] * Please make sure you edit your config file completely. " is from not following the advice below.

Code: Select all

# You MUST remove this line for your bot to start. This has been added to
# prevent you from starting up a bot that is not fully configured. Bots
# that have not been fully configured may join the wrong IRC network, the
# wrong channels, or generally do things that you do not want. Please make
# sure that you have double-checked every setting. There's also a similar line
# lower down, just to make sure you're reading :)
die "Please make sure you edit your config file completely."

Code: Select all

# Comment out this next line. Otherwise, your bot won't start.
die "You didn't edit your config file completely like you were told, did you?"

These are here to keep you from trying to run a malconfigured bot and throwing it onto an active irc network. This could cause havoc. So to prevent this, in 2 or 3 spots there are some DIE commands sprinkled. Simply #comment them making them harmless and make sure you are reading/editing your config _COMPLETELY_ otherwise we can't help you if you can't even help yourself.

audi · Post by **audi** » Wed Jun 24, 2009 1:29 am

Actually i dont know how and where to edit configuration file:(
am badly hanged:(

Mewbie · Post by **Mewbie** » Fri Jun 26, 2009 6:02 am

I think the easiest way for you to do this (apart from searching on sites to learn about eggdrop conf files) Is login to your shell via ftp, (in your ftp tool/ options depending on your shell provider, protocol might be SFTP) and download to your box the 'bots.conf' file.
You find this file in your bot's root directory.
For example: /home/yourname/botsname/bots.conf

Open that with wordpad and start reading. You'll learn a lot just from that one file

Further more in that file it will tell you which lines to remove.

Btw, if a line is preceded with: #
It's called 'commented'. This means that the program won't read whats on that line. Its generally instructions for the user or various optional commands.

So to 'uncomment' a line is simply to remove the preceding: #

It's also good to have a look around via FTP- get to know the paths and whats on there.

username · Post by **username** » Fri Jun 26, 2009 5:31 pm

This is the simplest way to solve your problem.