Ok, I've got a few questions here:
1) Let's say a new version of eggdrop comes out. How do I upgrade to the latest version without having to make install again?
2) If my host got changed and my eggdrop is not able to recgonise the new host, how should I get it to recgonise me? What is the command I should type? Is there anything I have to make changes in the .conf file?
Thanks
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
Upgrading to new Eggdrop version...
If I'm not wrong for your second question ..
You can do do one of this 2 things:
1) add a "--HOSTS your*!*host@in.here." in your userlist file and then "restart" the bot (if you can do a .reload you don't need the "restart" it).
2) If you binded from the .conf file the the "ident" msg command try a "/msg bot ident <password> [nickname]".
This should help.
<font size=-1>[ This Message was edited by: caesar on 2001-12-05 04:21 ]</font>
You can do do one of this 2 things:
1) add a "--HOSTS your*!*host@in.here." in your userlist file and then "restart" the bot (if you can do a .reload you don't need the "restart" it).
2) If you binded from the .conf file the the "ident" msg command try a "/msg bot ident <password> [nickname]".
This should help.
<font size=-1>[ This Message was edited by: caesar on 2001-12-05 04:21 ]</font>
ceasar - solution couldn't solve it. That is part of the problem. The inability to get to the partyline, because he recognised.
As for the first problem.
Download the bot version.
Kill your previous bot.
compile as normal, and "make install" directly over the top of your existing version.
Read over doc/UPDATES1.6 to see what has been changed.
Read over the config files, and find out what you is missing between yours and the newer version, and change as needed.
Start newer version
Note: you should make sure you have a backup of your config, user, chan, notes files before you do this.
As for the first problem.
Download the bot version.
Kill your previous bot.
compile as normal, and "make install" directly over the top of your existing version.
Read over doc/UPDATES1.6 to see what has been changed.
Read over the config files, and find out what you is missing between yours and the newer version, and change as needed.
Start newer version
Note: you should make sure you have a backup of your config, user, chan, notes files before you do this.
Well I know cos I use this when there is no other way to resolve a problem like that. Is not so good but an other one I don't know right now. Btw with ".reload" I ment if there is an other user who has dcc access to do that ".reload". He should try the "ident" command if he binded t from the .conf file, else try my "restart" or do I don't know what. 