unleaflike behavoir?

nicks0r · Post by **nicks0r** » Thu Aug 26, 2004 3:58 am

*** Disconnected from: slacker. unleaflike behavior (lost 1 bot and 0 users)

keep getting this error, all the flags are set correctly, any ideas?

nicks0r · Post by **nicks0r** » Thu Aug 26, 2004 5:54 am

also to go along with this problem i have leafs rejecting eachother?

[23:47] <slack3r0> [09:52] slacker rejected maiden

Wcc · Post by **Wcc** » Thu Aug 26, 2004 6:39 am

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.

nicks0r · Post by **nicks0r** » Thu Aug 26, 2004 1:23 pm

but all i upgraded was the hub

Alchera · Post by **Alchera** » Thu Aug 26, 2004 7:56 pm

It's best toupdate the whole net.

evildude · Post by **evildude** » Thu Aug 26, 2004 11:37 pm

Aww crap, I still have 2 bots using 1.6.15 for ipv6

Wcc · Post by **Wcc** » Fri Aug 27, 2004 8:26 am

Alot of people seem to be having problems with this. I'll write a patch today for 1.6.17 and post it here.

evildude · Post by **evildude** » Fri Aug 27, 2004 8:32 am

You rock dude! I'll be waiting patiently so that I can relink my ipv6 bots.
Thanks a lot.

nicks0r · Post by **nicks0r** » Sat Aug 28, 2004 1:16 pm

well i downgraded to 1.6.16 and same problems
any idea where the madness stops?

Wcc · Post by **Wcc** » Wed Sep 01, 2004 5:47 pm

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.

evildude · Post by **evildude** » Wed Sep 01, 2004 7:34 pm

Umm...

AWS · Post by **AWS** » Sat Mar 25, 2006 9:56 pm

thanx helped

helix · Post by **helix** » Wed Jan 10, 2007 1:31 pm

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.

ZubaZ · Post by **ZubaZ** » Tue Sep 29, 2009 6:43 am

Yes, removing flags lo from hub solve the issue.