Hi, I have several questions, which I'd like to find the answers for. I've decided to put all of them into one topic to avoid generating many discussions. I hope you'll be able to help me. Thanks in advance for your responses!
I use IRCd 3.2.9 & Anope services 1.8.7. They are installed on a server running on FreeBSD 8.0.
IRCd is being launched from the root account, and the services start under normal user privileges.
1. Which way is it better to generate permanent virtual hosts (vhost) for users? How do I make the vhost to apply right after user identification?
2. Hosts that were banned using Gline & Kline, disappear from the database after IRCd restart, how can I fix this?
3. Large messages are sent in blocks (especially private messages). I tried to enable RAW mode in services and use svsnolag but it did not work. How can i solve this problem?
4. Can I set the system up so that a registered nickname would change to "Guest" if it's not been identified in 60 seconds? (I mean a global rule, not one for a specified user).
Some questions, help please.
-
- Posts: 36
- Joined: Thu Dec 27, 2007 8:48 am
Re: Some questions, help please.
All the answers are in the documentations of each package. Read it.
PS: don't run any of this daemons as root.
PS: don't run any of this daemons as root.
-
- Head of Support
- Posts: 2085
- Joined: Tue Jun 15, 2004 8:50 pm
- Location: Chino Hills, CA, US
- Contact:
Re: Some questions, help please.
1) Consult Anope's HostServ documentation, it's a setting either in each host or a global setting in the conf.
2) Use OperServ AKILL.
3) That's how Unreal works. It's a protection.
4) Consult NickServ's documentation. (There's a configuration item for default nick settings for new nicks, I think it was like NSSetKill or something).
I think that's all.
Oh yeah, don't run stuff as root.
2) Use OperServ AKILL.
3) That's how Unreal works. It's a protection.
4) Consult NickServ's documentation. (There's a configuration item for default nick settings for new nicks, I think it was like NSSetKill or something).
I think that's all.
Oh yeah, don't run stuff as root.
Re: Some questions, help please.
Thanks for your answers!
As far as i understand it was possible to fix this in earlier versions, was not it?
http://unreal.x-tab.org/faq#nofakelag
Is it possible to disable this protection feature? It is very inconvenient.
As far as i understand it was possible to fix this in earlier versions, was not it?
http://unreal.x-tab.org/faq#nofakelag
Is it possible to disable this protection feature? It is very inconvenient.
Re: Some questions, help please.
Open include/config.h in the editor of your choice.Laterport wrote:Thanks for your answers!
As far as i understand it was possible to fix this in earlier versions, was not it?
http://unreal.x-tab.org/faq#nofakelag
Is it possible to disable this protection feature? It is very inconvenient.
Locate the line that reads: #undef FAKELAG_CONFIGURABLE
Read the warning above this line. Keep in mind we are not responsible for server crashes caused by changing this setting.
Change the line so it reads: #define FAKELAG_CONFIGURABLE
Save the file, and return to the main Unreal directory.
Run: make clean all
Run make install if needed.
Restart Unreal.
------
To configure your server to exempt certain people, follow these steps:
In unrealircd.conf, create a new class. Set the options as you please.
Specify class::options::nofakelag in your new class block.
Create an allow block, be sure to specify BOTH IP and host, otherwise it may match everyone. Read "about matching" in the Allow Block section of Unreal's documentation for more information.
Rehash the server and have the affected users reconnect.
"Heart + Determination + Perserverence = Success"