StartingUnrealIRCD under Debian!

[SpoiLeD]

Hi you all!

If have a weird problem, we are trying to get 4 servers linked, and i'm the only debian server! I've manged to get unrealircd compiled and started fixing the config. When i had done this i started ircd, and i got this error.

Code: Select all

debian:/home/nick/Unreal3.2# ./unreal start
Starting UnrealIRCd
./unreal: line 10: /home/nick/unreal3.2/src/ircd: No such file or directory
Possible error encountered (IRCd seemily 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
=====================================================

./unreal: line 10: /home/nick/unreal3.2/src/ircd: No such file or directory

Will i tryed to figure it out i found out that /src/ircd was a file that was a compiled file. So i changed its name and created a directory.. i started unrealircd again.. and got the same error. I looked the config over but couldnt found anything..

Then i looked in the unreal file where the error came from. But nothing weird there... Could someone help me out!

Tnx in Advance

- SpoiLeD

[Syzop]

You understand case sensitivity, right?

/home/nick/Unreal3.2
is a completely different directory than
/home/nick/unreal3.2

For some reason I doubt you did that on purpose (though, possible).
So for a quick fix, remove the unreal3.2 directory with lowcase u ('rm -rf /home/nick/unreal3.2'), and then from the /home/nick/Unreal3.2 directory do:

Code: Select all

make clean; rm config.settings; ./Config -quick && make

[Stealth]

What does ./Config -quick do?

[SpoiLeD]

You understand case sensitivity, right?

/home/nick/Unreal3.2
is a completely different directory than
/home/nick/unreal3.2

Yap i do, but there was no dir like unreal3.2.. the only dir excisting was Unreal3.2..

But the tip was great, it works now , thanks for your help!

Thanks Syzop!

[Syzop]

What does ./Config -quick do?

It runs ./Config without asking any questions, using the settings from config.settings (saved from previous ./Config runs), or otherwise the default settings.

It's mainly meant for cases like: when you know the ./Config settings are (or were) correct, for example if you are upgrading 12 servers and ran ./Config already on 1 of them to see what's new/what got changed ;).
Also, because this way you don't see the release notes, I always suggest to read them on your own if you haven't done so yet.

Naturally, I don't suggest to use ./Config -q(uick) for every upgrade or so, it's better to just run ./Config and see if any new questions were added. Pressing ENTER like 15 times is no sin ;)