mush.cnf

Posted by Joris Slob on Sat 16 Mar 2002 01:07 PM — 5 posts, 20,805 views.

#0
Sorry for another newbie question.

I have just downloaded the pennmush172p29 archive with the Win32 compiled version. I have follewed the instructions from the readme that was included in this archive. My server is running now, and I can log in with a client. The only thing bothering me is a line in the game.log

CONFIG: Invalid command or restriction for @toad.

I have looked up where this came from in the mush.cnf and if I comment out this line this warning goes away.

restrict_command @toad nobody

The newbie question is... will I be seriously messing something up if I comment out this line?

Thanks for any replies...
Joris
Australia Forum Administrator #1
I doubt if that will cause a problem. The problem is probably caused by the @toad command not existing (maybe been removed in that version). If it doesn't exist it won't really matter if you don't restrict it. Try typing @toad <someone> and see what happens.
#2
Thanks! That was it. @toad doesn't have a help file, and doesn't work. Like the comment said, we should probably be using @boot and @nuke anyhow.
USA #3
Hi~

I have downloaded, installed, run and successfully
logged on to PennMUSH on my PC with MushClient,
using TCP/IP 127.0.0.1 @ Port 4201.

I still see the error message below when I run it :

ERROR: Cannot open configuration file mush.cnf

Where is this file, or how do I go about creating it?

Thanks.
USA #4
I should mention that I tried renaming mushcnf.dst to
mush.cnf earlier, and it didn't work.

I just tried re-opening it with notepad, and saw that
it was named mush.cnf.cnf.

I changed it to mush.cnf, and no longer have that error
message.

I have also changed the files alias, restrict, & names
by means of the same method -first, delete the dst, and
second, put a period between <filename> and the suffix cnf.