OK,
You are right, this was wrong and was a result of trying everything I
could think off to get it running. But even when fixed this did not
solve the problem.
Because the error message said it couldn't write the PID file, I was
searching for problems with writing the PID file. Pretty obvious right?
Well it seemed to be something completely irrelevant. Because I also had
the following line in my config:
<server name="irc-server" description="IRC Server" network="MyNetwork">
As you can see NAME is not an valid Domain-Name, which it should be (but
didn't know then). And therefore Inspircd throws an error about not
being able to write the config file.
I suggest to change the severity of this bug to low. Because the server
starts fine when your config has no problems. But I think it should
throw an relevant error if the config do has problems.
On 02-06-13 22:29, Guillaume Delacour wrote:
Problem with "/" ^
You've edited your configuration and add a slash before ">", this is why
inspircd fails to start (reproduced with wheezy chroot). The correct
(package default) directive might be :
<pid file="/var/run/inspircd.pid">
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
