problem with startup

Okay my mud compiles then I do ./startup & but it wont let me log on. So i try to do make clean and make and both say the mud is running. Why wont it let me log on if its running?

What do you mean, you can't log on? Did you create a character and it's refusing it? Or are you unable to use the default character? Did you follow the instructions in the documentation regarding how to set up the first player? You could also try searching these forums, or even Google; this question has been asked/answered many times.

no when i try to connect it wont let me connect it keeps saying connection timed out

It's cause you've been banned.

Check which port it is running on. I think the startup script defaults to 5000.

Smaug usually defaults to port 4000.

Yeah maybe I changed it on mine. :)

You can see if it is listening on Linux like this (as root):



This shows that smaug is listening on port 4000.

On Windows, try "netstat -a" - that seemed to show listening ports for me.

i already know how to see the port i just go and alter it in startup. But as i said it says its refusing the connection and i dont know why. Question after i do ./startup & how do i shut it down with out entering the mud. closing the CYGWIN window doesnt work. If the case is im banned how do i unbanned myself with out entering the mud.

Yes, that shows the port it is trying to start up on. Netstat shows if it succeeded. Connection refused may well mean it didn't start.

In Cygwin, I type this (after succesfully starting it):



The entry for 0.0.0.0:4000 shows it is running (listening for connections) on port 4000. You need to do that to confirm it is actually running.



You can find its process id:



Then kill that process id:



Although I found that with startup running Smaug came back a moment later lol because that is what startup is designed to do...



So you could spend all day killing them. :)

Next step, find and kill startup:



Now kill startup:




Once you have killed startup, check if smaug itself is still running and if so, kill that. Then it shouldn't reappear.

I found I had to comment out two lines in startup, or it didn't start up:



That is because it didn't find the "limit" command in my copy of Cygwin. Perhaps that is your problem?

i cant kill the mud with -9 212 with cygwin it keeps saying no such process

What client are you using to try and log onto the MUD?

Are you sure you are using localhost, and the right port?

The number 212 was taken from the example above. Typing "jobs -l" tells you the process IDs, then you kill that number. It won't always be 212.

You can also check what port your mud is running on from the logs. ^^