View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004512 | unreal | ircd | public | 2015-12-27 22:04 | 2016-05-22 21:30 |
| Reporter | pchevee | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 4.0.0 | ||||
| Summary | 0004512: die, restart : not enough privileges | ||||
| Description | As I am Netadmin, the system tells me that I have not enough privilege to die or to restart the server. Nevertheless I can do it manually in the shell window. | ||||
| 3rd party modules | |||||
|
|
Having a look - to be clear, are you using the default oper classes and using that netadmin, or do you have your own netadmin? |
|
|
The fact that die and restart privileges are missing are intentional. I wonder why anyone would use these, other than on a test network. But there are two bugs in one bugreport.. that isn't ideal. |
|
|
Other issue split off to 0004518. |
|
|
What do you think, Travis? A quick query in #unreal-support the other day revealed two others also only use DIE and RESTART on test networks. It's really no hassle to include them in netadmin. I'm just wondering what's the right choice. I left it out for a reason, not by mistake. pchevee: where did you use it for? In what situation did you use DIE or RESTART? (and which one) (bug set to Feedback to gather some.... feedback from everyone) |
|
|
Turns out the people in #unreal-support who were using DIE or RESTART were only doing it because they either thought restarting was necessary (which wasn't) and bug 0004520 which caused ./unrealircd [stop|restart] not to work if you installed UnrealIRCd in a non-default directory. I don't think other services have a kill or restart button that you can trigger over the (same) protocol. Apache, mysql, samba, proftpd, .... if we were different for some reason I can understand but what would be different about an IRCd? If anything it is the fact that a restart or die has much more consequences, which only favors not having the option. Another possible problem with RESTART is that if you have a configuration problem and no shell access - eg: some previous person edited the config file and rehashed but didn't notice there was a parse error - it may leave your IRCd "dead": it will stop but not start. And well DIE is just.. why would you want to use that... |
|
|
Burn both commands >:-) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-12-27 22:04 | pchevee | New Issue | |
| 2015-12-28 00:56 | tmcarthur | Note Added: 0018955 | |
| 2015-12-28 00:56 | tmcarthur | Assigned To | => tmcarthur |
| 2015-12-28 00:56 | tmcarthur | Status | new => assigned |
| 2015-12-28 17:03 | syzop | Note Added: 0018965 | |
| 2015-12-28 17:05 | syzop | Issue cloned: 0004518 | |
| 2015-12-28 17:06 | syzop | Note Added: 0018966 | |
| 2015-12-28 17:06 | syzop | Status | assigned => feedback |
| 2015-12-28 17:06 | syzop | Summary | die, restart : not enough privileges. In addition, pb of hostname resolution => die, restart : not enough privileges |
| 2015-12-28 17:06 | syzop | Description Updated | |
| 2015-12-28 17:31 | syzop | Note Added: 0018971 | |
| 2015-12-28 17:32 | syzop | Note Edited: 0018971 | |
| 2015-12-29 11:50 | syzop | Note Added: 0018986 | |
| 2015-12-29 14:20 | blank | Note Added: 0018991 | |
| 2016-05-22 21:30 | syzop | Status | feedback => closed |
| 2016-05-22 21:30 | syzop | Assigned To | tmcarthur => |
| 2016-05-22 21:30 | syzop | Resolution | open => no change required |
