unrealircd.conf configuration on ubuntu

[apocr4l1pt0]

hi to all ( sorry for my bad english im italian)

i have a problem to configure the file unrealircd.conf:
Ecco qua che mi esce fuori ( un casino di errori xD )
-----------------------------------------
* Loading IRCd configuration ..
* unrealircd.conf:71: Ignoring extra data
* unrealircd.conf:71: Ignoring extra data
[warning] unrealircd.conf:255: listen with SSL flag enabled on a non SSL compile
[error] unrealircd.conf:322: link hub.mynet.com with SSL option enabled on a non-SSL compile
[error] unrealircd.conf:322: link hub.mynet.com with ZIP option enabled on a non-ZIP compile
[error] unrealircd.conf:538: tld::motd: ircd.motd.fr: No such file or directory
[error] unrealircd.conf:539: tld::rules: ircd.rules.fr: No such file or directory
[error] unrealircd.conf:738: set::kline-address must be an e-mail or an URL
[error] 5 errors encountered
[error] IRCd configuration failed to pass testing
Possible error encountered (IRCd seemingly not started)
=====================================================
Check above for possible errors, and this output of
ircd.log. If you cannot solve the problem, read
Unreal.nfo on where to get support
=====================================================
tail: cannot open `/home/admin/Desktop/Unreal3.2/ircd.log' for reading: No such file or directory
-----------------------------------------

How Can i resolve these errors ? Help me PLEASE


Thanks

[Bunkerwaiss]

1. Grab the code from line 60 to 80 and paste it here.
2. Your listen block (near line 255) has the SSL option enable, remove it, should look like:

Code: Select all

listen         your.server.ip:6667
{
	options
	{
		clientsonly;
	};
};

3. Near line 322 check the link block, has the SSL and ZIP options, remove it, should look like:

Code: Select all

link hub.mynet.com {
	username *;
	hostname 1.2.3.4;
	bind-ip *;
	port 7029;
	hub *;
	password-connect "LiNk";
	password-receive "LiNk";
	class servers;
	options {
		autoconnect;
	};
};

4. Create two files (ircd.motd.fr) and (ircd.rules.fr) and place it in your Unreal root folder
that is, here:

Code: Select all

/home/admin/Desktop/Unreal3.2/

5. Finally go near the line 738 and find this:

Code: Select all

set {
	kline-address "[email protected]";

And fill it with your email, or your server email address..

6. READ THE DOCUMENTATIONS.

[Stealth]

I also suggest removing all the comments you don't need (which should be all of them). A configuration file should never have more than 700 lines unless you're running a large network and using the advanced features of Unreal.

[katsklaw]

I suggest breaking unrealircd.conf up into several files so it makes managing servers easier.

Case in point you have unrealircd.conf contain all your server specific settings, a file called network.conf contain all the stuff that absolutely must be the same on all servers and another file called links.conf which has link blocks for all servers. links.conf can also be done in role based fashion. For example hub.conf for dedicated hubs can have link blocks for all other hubs/services where as leaf.conf can be given to server admins that have leaf servers and dont need to know all the other servers. The convenience of this is seen when trying to manage serveral servers by yourself of in a small group. Newly linked servers are emailed the network files which will be the same for all servers anyway and cuts out writing configs for all servers.

My personal favorite is to make all servers hubs and have all servers have link blocks for all other servers so i can route the net as I want without needing shell access to all the server shells. You can take that a step farther and use secured remote includes as well and then remote include the network settings, Net Admin oper blocks, link blocks etc. In the event that the remote included conf can't be reached, then the worst thing that happens is servers can't be /rehashed. Very small price to pay for the convenience created. I also don't believe in local opers so i also include O:Lines globally in remote included files so all opers can oper on all servers. This allows for tighter integration as well as better control over opers at the network level. The convenience of this is seen when you nest remote included files and take advantage of remote rehashing.

This all may sound very advanced, but when you take a few minutes to understand how this works and take one step at a time as well as not getting in a hurry to open your new network to the public, you might see that it's not really all that complex after all.

I thought there was s tutorial on how to do remote includes on these forums beyond just compiling. If not I'll look into writing one so others that believe as I do can take advantage.

As far as #6 goes, I don't think this is as much of an RTFM issue as it is a "read the error message completely" issue.