Hello, I got a few servers I can run a MuD on now, And I been wanting to it forever. I have experience with coding Talkers years ago, But My C is a bit shaky, So I'm looking for some advice on tutorials and a pretty basic codebase. I have tons of idea's , Just need a bit of help. I never compiled my own MuD before, Just played them for years. So if anyone is willing to help out Id appreciate it.
You can check out my Talker at Telnet://presidium.org:5555 Or e-mail Syphon101@gmail.com.
Im not sure what Im doing wrong, but first off I tried to ./configure and make install, on a friends linux box. That didn't work, So next I tried manually, Now I followed the instructions for that, Not to sure what they ment about copying the "driver" file into $MUDHOME/bin/ cause I don't even know what file is the driver file, If that's what they mean. But I followed the Instructions, changed the two lines in mudos.cfg, mudlib directory and binary directory. Then I edited startmud, Then when I went to type ./startmud, I got nothing. Id be greatful If sombody would help me out with this considering how much I just read on this codebase.
I can telnet in but when I ./startmud it keeps repeating this socket_connect: requested on: 126.96.36.199 23 socket_connect: socket already bound to address/port: 188.8.131.52/0 socket_connect: requested on: 184.108.40.206 23 socket_connect: socket already bound to address/port: 220.127.116.11/0
when I run ./startmud I get this
DeadSoulsNew (MudOS v22.2b14) starting up on Linux - Thu Nov 16 23:54:19 2006
Connection to address server (localhost 9999) refused.
Sounds like it's trying to load the mud twice there, first time on port 9999 and the second time, because that port's already in use, it's defaulting to port 5555, but it also looks as though it's not sending it's output to a log file for you. Having never used DS before, I'm not sure what else to offer on this one, yu might just have to wait for Cratylus' input, but it is probably at least worth opening your startup script file and checking that it's not calling the mud's executable twice and that it is sending the screen output to a log file.
So, just from curiosity, given the error he reported, was it that he was running the startup script twice or did he just use it with the wrong parameters?
I'll grant that I usually use nohup ./startup & rather than just ./startup, to start my mud, but ./startup with work too.. but then I'm running smaugfuss not deadsouls, so maybe the startup script for DS needs a command line parameter. *shrug*
Also, doesn't deadsouls spam a logfile rather than the screen like that? With smaug you have to run the executable without the startup script to get all that screen spam.
TBH I'm not 100% clear on it, because I didn't get everything I'd need to say for sure.
However, based on the data he posted, it looked like the startup script had not been modified. It's necessary to add the absolute path of the mud to the script, or weird things like looping startups can happen.
My view on console spam is that the console is sometimes a quick and effective way to troubleshoot. I'm just used to getting a lot of startup information, because (to me) it's a convenient way to identify problems. Once the mud is up, the console gets mostly only network errors, and messages specifically intended by the admins to be directed to the console. One of the pieces of advice Syphon got was to skip using the script and call the binary from the command line, with this command:
Was mainly just curious, so thanks for sharing what info you did know about it Crat. I don't know that output to the console is a bad thing, and certainly not that it's broken, but as you say, not what I'm used to.