Member Discussions

I got the RoT 1.4 codebase from mudmagic (The one that is cleaned for GCC4) and it compiled with not a single error or warning, but I cant seem to start it up. None of the commands I use work such as ./startup & nohup ./startup & also the ./startup with the port and than & Keeps telling me that it isnt an area :-/ Anyone know whats wrong here?

You might post the actual messaging that you get if no one knows off the top of their head what the problem is?

This is what all I tried and the messages I get back.


[chris.m@localhost area]$ ./startup &
[1] 25024
[chris.m@localhost area]$ /Rot/area: No such file or directory.
[chris.m@localhost area]$
[1]+ Exit 1 ./startup


[chris.m@localhost area]$ ./startup 4000 &
[1] 25032
[chris.m@localhost area]$
[chris.m@localhost area]$ /Rot/area: No such file or directory.

[1]+ Exit 1 ./startup 4000
[chris.m@localhost area]$


[chris.m@localhost area]$ nohup ./startup &
[1] 25038
[chris.m@localhost area]$ nohup: ignoring input and appending output to `nohup.out'

[1]+ Exit 1 nohup ./startup
[chris.m@localhost area]$


[chris.m@localhost area]$ nohup ./startup &
[1] 25038
[chris.m@localhost area]$ nohup: ignoring input and appending output to `nohup.out'

[1]+ Exit 1 nohup ./startup 4000 &
[chris.m@localhost area]$


(Comment added by JBE1987 on Thu Aug 28 7:38:16 2008)

Nevermind guys, I found a QuickMUD code that is also 100% clean and am using that now and it runs just fine, but thanks for the help. :)

Disclaimer: I'm going off of my knowledge of ROM, and I'm pretty sure RoT is a ROM Deriv. so with that said, I'll do my best to help.

The message you are looking for in order for it to be working is this:

nohup: appending output to `nohup.out'

'nohup ./startup &' Is what I use (minus the quotations of course), and you are doing right by doing it from the area directory (or at least it looks like that's where you are doing it from, if not, that's where you need to be).

I downloaded the codebase and took a look. The best I can think of is that the path to the area folder might not match. Is your MUD contained in a 'Rot' folder? If not, then I'd suggest one of two things..

Either get the MUD folder that contains your area file renamed to Rot, or edit your startup file to point toward the correct path to the area folder.

Try one of those and see if that helps... if not, I'll see if I can't find something else that might be happening, or maybe someone else will chime in with a better suggestion.

Not sure how to edit the startup script since Ive never had to do it before. Also yes, there is a rot.are in the area folder, don't know if thats what you meant. I put in a startup code from my old Rom code and it works a bit better, but still doesnt boot it up, so Ill just put in the old RoT startup code so I can do what you say.

The RoT startup script is looking for the 'rot' file in the /bin directory. It will delete the current one and copy the new one. I imagine the Makefile is designed to place the finished compile in /bin, as well.

This is different from ROM, where you have to copy the 'rom' file over manually to the /area dir from the /src dir.

Not sure how to edit the startup script since Ive never had to do it before. Also yes, there is a rot.are in the area folder, don't know if thats what you meant. I put in a startup code from my old Rom code and it works a bit better, but still doesnt boot it up, so Ill just put in the old RoT startup code so I can do what you say.

No, what I meant is what folder is your /area folder contained in? As in what path?

My MUD is named End of Time, and its abbreviated 'eot' so the path in my game is:

/eot/area or /eot/src etc.

The startup script is looking for the area folder, and the default path is: /rot/area

So, in order to get RoT to load for me, I'd either have to rename my eot folder to rot, or change the startup script from '/rot/area' to '/eot/area'

So whatever folder your MUD is contained in, basically, is the path the startup script needs to be pointing toward.

For editing files in Linux (assuming you are using Linux) take a look at this:

http://kianga.kcore.de/2004/10/03/linux_faq

nano/pico are useful tools for editing files.

I'm at work and my break is over, so I gotta go. Good luck!