h4tr3d wrote:Ok, i understand that the first person who /opers is +o'd and than pulled to #Opers .. And When I do it thats what happens.. but when my friend does it.. hes puleld to #Oper .. but inside the oper.. he cannot +O himself .. nor can he become operator....... :S on other linux servers.. this same thing has not happend..... i guess my final question is... how can i change this to work, the way i want it too?
I'm only going to explain this one last time, but I'll do it differently.
1> you type: /oper name password
2> The ircd validates your credintials and since all is good it sets you
umode +o (global ircop)
3> the ircd then forces you to join #Opers, where then you are granted
chanmode +o (chanop)
4> your friend types: /oper name password
5> The ircd validates their credintials and since all is good it sets them
umode +o (global ircop)
6> the ircd then forces them to join #Opers, where then they are
NOT granted
chanmode +o (chanop) because the channel is not empty!
7> Since you have no services, they have to be opped (chanop, chanmode +o) by you or another ChanOp, they can NOT do it themselves with the /mode cmd
This is where you are stuck.
Now, there IS a command that services admins (umode +a) can use and that is /samode, try:
/helpop ?samode for more information. You can also add the can_override flag to your oper block, it does seem to be missing, I can't promise that will "fix" it as you say since I don't believe in overrides.
Peace