Page 2 of 2
Posted: Sun Oct 03, 2004 2:45 am
by Err0r
okay i think my conf was messed up, but for somereason the mirc still worked, i uninstalled and reinstalled and remade the conf, and add exactly like stealth said and i got it to work! thanx alot man!
Posted: Sun Oct 03, 2004 4:14 am
by jewles
LoL, believe me I could be a hell of a lot more "impolite"... you are right... not all the questions are covered... however yous are!
Posted: Mon Oct 04, 2004 4:51 am
by Err0r
yes but never worked, it was the first thing i checked!!!!!!!!!
some people just dont understand, when people have problems i never tell them to refer to the FAQ, mainly here because this is a support thread, your suppose to support people, not flame them
Posted: Mon Oct 04, 2004 12:43 pm
by w00t
The idea is... they read the documentation first, then ask for support. The documentation has been written for a purpose.
Posted: Mon Oct 04, 2004 6:11 pm
by katsklaw
Yarou wrote:Oper block for the umteenth time.
Perhaps, but the first time on this thread .. thanx.
Posted: Mon Oct 04, 2004 6:13 pm
by katsklaw
Err0r wrote:wow w/e happen to people being polite, or thinking maybe documentation dont have all the answers!
That would be fine but the provided docs cover this exact problem.
Posted: Tue Oct 05, 2004 2:10 am
by Err0r
i kinda liked it here til you were all assholes in my point of view, i undersand it gets annoying helping people but if you dont like then dont FU**ing do it!
I SAID! ill put it in caps so you can read it! I READ THE DOCS FU**ing FIRST!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
THEY HELPED ME ABOUT AS MUCH AS HAVING CRABS HELPED ME THEY DID NOT ADDRESS MY PROBELM! my problem had to do with something other the the o-line, i had to reinstall UNREAL
i tried being nice, i liked being here and wanted to help others but you ruin all my damn fun!
Posted: Tue Oct 05, 2004 2:50 am
by katsklaw
appearently you missed the explanation of the oper block that states
oper <name> {
Then it explains what <name> means.
The oper:: specifies the login name for the /oper.
The above is found in the unreal32docs.html file in the doc directory of every unreal tarball that I can remember.
The example.conf says (also found in the doc directory)
The syntax is as follows:
oper (login) {
Then it even gives you an example
oper bobsmith {
So how can the above be confusing? What part of: 'oper Err0r {' was the problem? wiretapp pointed the error to you 14 posts ago immediately after your oper block was pasted as requested.
Since your problem is a config problem you did NOT have to re-install unreal .. you CHOSE to do so.
Same problem
Posted: Mon Oct 11, 2004 5:09 am
by SineSwiper
I'm getting the same problem. No, it's not a case issue. Here's the oper block:
Code: Select all
oper admin {
class clients;
from {
userhost *@*;
};
password "blahblah";
flags
{
netadmin;
global;
can_override;
};
};
Here's the commands I've tried:
/stats o
Permission Denied- You do not have the correct IRC operator privileges
/stats O
Permission Denied- You do not have the correct IRC operator privileges
/rehash
Permission Denied- You do not have the correct IRC operator privileges
/oper admin blahblah
No O-lines for your host
Yeah, I make sure to save config changes, restart the server, and reenter the server when I mess with the oper block.
Posted: Mon Oct 11, 2004 5:38 am
by SineSwiper
Found the problem. The "./unreal restart" command is misleading and doesn't work as expected. Apparently, a SIGINT doesn't actually reload the config file. I noticed this when I tried a stop & start, and suddenly I couldn't log in. (This was due to a recent screw up on my allow blocks.)
After experimenting with config changes using a stop & start, it would actually reload the config this time.
I will submit this as a bug, if not already pre-existing.