| View previous topic :: View next topic |
| Author |
Message |
nicks0r Guest
|
Posted: Thu Aug 26, 2004 3:58 am Post subject: unleaflike behavoir? |
|
|
*** Disconnected from: slacker. unleaflike behavior (lost 1 bot and 0 users)
keep getting this error, all the flags are set correctly, any ideas? |
|
| Back to top |
|
 |
nicks0r Guest
|
Posted: Thu Aug 26, 2004 5:54 am Post subject: |
|
|
also to go along with this problem i have leafs rejecting eachother?
[23:47] <slack3r0> [09:52] slacker rejected maiden |
|
| Back to top |
|
 |
Wcc Master
Joined: 28 Oct 2001 Posts: 278 Location: USA
|
Posted: Thu Aug 26, 2004 6:39 am Post subject: |
|
|
| See the release notes for 1.6.17. If you're sharing userfiles, and you upgrade any of the leafs, all the hubs need to be upgraded too. It's best toupdate the whole net. |
|
| Back to top |
|
 |
nicks0r Guest
|
Posted: Thu Aug 26, 2004 1:23 pm Post subject: |
|
|
| but all i upgraded was the hub |
|
| Back to top |
|
 |
Alchera Revered One

Joined: 11 Aug 2003 Posts: 3344 Location: Ballarat Victoria, Australia
|
Posted: Thu Aug 26, 2004 7:56 pm Post subject: |
|
|
| Quote: | | It's best toupdate the whole net. |
_________________ Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM |
|
| Back to top |
|
 |
evildude Voice
Joined: 03 Feb 2004 Posts: 24
|
Posted: Thu Aug 26, 2004 11:37 pm Post subject: |
|
|
Aww crap, I still have 2 bots using 1.6.15 for ipv6
 |
|
| Back to top |
|
 |
Wcc Master
Joined: 28 Oct 2001 Posts: 278 Location: USA
|
Posted: Fri Aug 27, 2004 8:26 am Post subject: |
|
|
| Alot of people seem to be having problems with this. I'll write a patch today for 1.6.17 and post it here. |
|
| Back to top |
|
 |
evildude Voice
Joined: 03 Feb 2004 Posts: 24
|
Posted: Fri Aug 27, 2004 8:32 am Post subject: |
|
|
You rock dude! I'll be waiting patiently so that I can relink my ipv6 bots.
Thanks a lot.
 |
|
| Back to top |
|
 |
nicks0r Guest
|
Posted: Sat Aug 28, 2004 1:16 pm Post subject: |
|
|
well i downgraded to 1.6.16 and same problems
any idea where the madness stops? |
|
| Back to top |
|
 |
Wcc Master
Joined: 28 Oct 2001 Posts: 278 Location: USA
|
Posted: Wed Sep 01, 2004 5:47 pm Post subject: |
|
|
Actually, I guess the best solution, if you don't want to/ cant upgrade your whole net, then ive bots +o for the CHANNELS they need to be opped on; not global +o.
The problem is that .17 forces a +o flag to automatically imply the +l user flag (halfop) as well. This uncovered a hidden bug that had been present for a long time, where part of the code see's no difference between botflag +l and userflag +l. It was fixed in 1.6.17, but, the +l being forced for +o bots makes this bug show up on all of the older bots.
Here's what I would do:
chattr all your bots -o and -l
do a .save
set private-globals "l" in your config (that's l as in L, not a one)
give your bots +o for the channel's they need it on
That should fix the problem. |
|
| Back to top |
|
 |
evildude Voice
Joined: 03 Feb 2004 Posts: 24
|
Posted: Wed Sep 01, 2004 7:34 pm Post subject: |
|
|
Umm...  |
|
| Back to top |
|
 |
AWS Voice
Joined: 30 Dec 2005 Posts: 9
|
Posted: Sat Mar 25, 2006 9:56 pm Post subject: |
|
|
| thanx helped |
|
| Back to top |
|
 |
helix Voice
Joined: 10 Jan 2007 Posts: 1
|
Posted: Wed Jan 10, 2007 1:31 pm Post subject: |
|
|
| nicks0r wrote: | well i downgraded to 1.6.16 and same problems
any idea where the madness stops? |
If You downgraded to 1.6.16
remove the l flag from the hub, then the madness stops. |
|
| Back to top |
|
 |
ZubaZ Voice
Joined: 25 Oct 2007 Posts: 2
|
Posted: Tue Sep 29, 2009 6:43 am Post subject: |
|
|
| Yes, removing flags lo from hub solve the issue. |
|
| Back to top |
|
 |
|