Displaying/referencing IRCops flags

These are old archives. They are kept for historic purposes only.
Post Reply
RusselB
Posts: 7
Joined: Thu Nov 09, 2006 12:52 am

Displaying/referencing IRCops flags

Post by RusselB »

I'm a NetAdmin on a network that currently uses UnrealIRCd 3.2.6
I also have access to modify the opers.conf file in order to add/remove opers, or change their flags.
I've done a fair bit of searching, and haven't been able to find what I want to know (possibly due to an incorrectly phrased search, if so, I apologize)

What I'm looking for, is a way for an IRCop to be able to recognize the specific flags for a named IRCop.
I realize that this may not be available, in which case, I will make a post in the bugtracker as a suggestion.

In case what I'm looking for isn't clear, it might be something like this.

Entry in opers.conf:
oper RKB {
flags
{
netadmin;
can_rehash;
can_die;
can_restart;
helpop;
can_wallops;
can_globops;
can_localroute;
can_globalroute;
can_localkill;
can_globalkill;
can_kline;
can_unkline;
can_localnotice;
can_globalnotice;
can_zline;
can_gkline;
can_gzline;
get_umodew;
get_host;
can_override;
can_setq;
can_addline;
can_dccdeny;
services-admin;
admin;
global;
};
};

Command: /flags RKB
Returns: netadmin; can_rehash; can_die; can_restart; helpop; can_wallops; can_globops; can_localroute; can_globalroute; can_localkill; can_globalkill; can_kline; can_unkline; can_localnotice; can_globalnotice; can_zline; can_gkline; can_gzline; get_umodew; get_host; can_override; can_setq; can_addline; can_dccdeny; services-admin; admin; global;

If anyone knows if this can currently be done (and how) please post with the information.
Stealth
Head of Support
Posts: 2085
Joined: Tue Jun 15, 2004 8:50 pm
Location: Chino Hills, CA, US
Contact:

Post by Stealth »

The only way this can be done without a module is to use /stats o. The part that looks something like "rhgwlcLkKbBnGAaNzWtZqd" is a list of the "old-style" flags. All you need to do is copy the chart from the docs and make it available to you opers to reference what is what.

Also, on a side note... To have everything enabled for an oper, you don't need to list EVERY flag, as some flags include others (like NetAdmin, Global, Local, Services-Admin, and Admin)... With this in mind,

Code: Select all

 netadmin;
can_rehash;
can_die;
can_restart;
helpop;
can_wallops;
can_globops;
can_localroute;
can_globalroute;
can_localkill;
can_globalkill;
can_kline;
can_unkline;
can_localnotice;
can_globalnotice;
can_zline;
can_gkline;
can_gzline;
get_umodew;
get_host;
can_override;
can_setq;
can_addline;
can_dccdeny;
services-admin;
admin;
global; 
becomes

Code: Select all

 netadmin;
can_die;
can_restart;
can_zline;
can_gkline;
can_gzline;
get_umodew;
get_host;
can_override;
can_addline;
and still gives that oper the ability to do everything, which is much shorter in the conf and easier to manage. I suggest you look at the table in the docs to see which flags include more automatically.
RusselB
Posts: 7
Joined: Thu Nov 09, 2006 12:52 am

Post by RusselB »

Thanks for the reply, and that will do just great for what I've got in mind.

Regarding having every flag listed, I realize that about the different levels including certain flags/levels automatically...I just made up the entries in that post as I was going along, not really paying much attention (frankly I'm surprised I didn't enter something that isn't a valid flag)
Post Reply