View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001809 | unreal | ircd | public | 2004-05-11 19:26 | 2004-05-16 11:56 |
| Reporter | Brad | Assigned To | |||
| Priority | normal | Severity | tweak | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Product Version | 3.2 | ||||
| Summary | 0001809: Services Admin OLine structure | ||||
| Description | Why is it in the IRCd a services oper (admin?) is considered higher than a (Co) Server admin? A lot of admins I know think it's silly to have services admin higher up than a (Co) server admin, Unreal is the only IRCd I recall that has services admins higher up than most other admins. Personally I think it should go something like this: Net Admin Server Admin Co Server Admin Services Oper (soon to be admin?) IRCop Local IRCop I can't think of a reason why it a SA should 'outrank' anyone besides a global IRCop. | ||||
| 3rd party modules | |||||
|
|
Because a services admin usually has A LOT of power - networkwide (certainly exceeding any serveradmin that isn't SA). I think the current place is exactly where it should be :). |
|
|
I can. Server admins can do stuff, agreed. But the real power is in services... (unless personal ulines are possible?? :P) |
|
|
This model was adapted from DALnet. On DALnet, just because you're an admin doesn't mean you have access to services. Services give you much more power. I have no intention of changing this. |
|
|
Jolly good. |
|
|
I agree with codemastr |
|
|
/me calls for bug closure |
|
|
>(unless personal ulines are possible?? :P) There's a module for that actually (look at angrywolf's stuff). >/me calls for bug closure I second that motion ;) . |
|
|
I agree with codemastr too, but I just wonder about services operators. These DO exist (in anope ie.), but why doesn't they exist in UnrealIRCd? It really screws up the vhosts... |
|
|
Let's close this before it's too late :P. applet: we have no intentions to have both a services admin and a services operator level... because for operlevels it simply doesn't make sense or improve anything (what privileges should X have and what Y, and how does it differ from netadmin/sadmin/cosadmin/globop/locop). The levels we have now are simply enough. See #0001634 and 0000676 (=reverse order) if you are bored. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-05-11 19:26 | Brad | New Issue | |
| 2004-05-11 19:44 | syzop | Note Added: 0006174 | |
| 2004-05-11 22:02 | w00t | Note Added: 0006176 | |
| 2004-05-11 22:33 |
|
Note Added: 0006182 | |
| 2004-05-12 00:35 | w00t | Note Added: 0006192 | |
| 2004-05-12 06:57 | vonitsanet | Note Added: 0006198 | |
| 2004-05-12 20:08 | w00t | Note Added: 0006218 | |
| 2004-05-13 13:33 | aquanight | Note Added: 0006240 | |
| 2004-05-16 11:51 | applet | Note Added: 0006277 | |
| 2004-05-16 11:56 | syzop | Status | new => closed |
| 2004-05-16 11:56 | syzop | Note Added: 0006278 |
