MUD Coding

Baram · 04-11-2006, 10:56 AM

Sounds like you might need to learn a bit about Linux commands before getting too far into it.

man unzip

That should give you all the information you need about why unzip isn't working(there are some args you need to supply).

As for the make errors, looks like problems in the code, namely that "crypt" isn't defined. Without seeing the code it's talking about, I can't really tell you what the problem is.

Disclaimer: Yes, I know I didn't give you/him the answer. You/he clearly stated you/he wanted to learn on your/his own, so I'm just pointing in the right direction.

NotL337 · 04-11-2006, 11:21 AM

No, thanks--that was indeed quite helpful. The server just went down, but when it comes back up I'll give it a whirl.

Although any help with the changing ports thing would also be appreciated.

Baram · 04-11-2006, 11:25 AM

I don't know that code base, but my guess would be there is a config file somewhere. Probably somewhere near the lowest level directory of the code.

Davairus · 04-12-2006, 12:12 AM

1) crypt problem

I'd suggest start there.. make sure you have the latest and greatest version of smaug of course, there are versions out with all the bugs fixed. Also search that forum for crypt as its been done to death there. I found a lot of answers.

2) setting port

Here is a startup script I found for rom a long time ago, smaug is a diku derivative so it should work for you. You'll probably recognise the author.

The name of the file is 'startup' and you put it in the area directory. Then to start the mud just nagivate there and type startup.

[code]
#!/bin/csh
# Written by Furey.
# With additions from Tony and Alander.

# Set the port number.
set port = 9000
if ( "$1" != "" ) set port="$1"

# Change to area directory.
cd ../area

# Set limits.
if ( -e shutdown.txt ) rm -f shutdown.txt

while ( 1 )
# If you want to have logs in a different directory,
# change the 'set logfile' line to reflect the directory name.
set index = 1000
while ( 1 )
set logfile = ../log/$index.log
if ( ! -e $logfile ) break
@ index++
end

# Run rom.
../src/rom $port >&! $logfile

# Restart, giving old connections a chance to die.
if ( -e shutdown.txt ) then
rm -f shutdown.txt
exit 0
endif
sleep 15
end
[/quote]

dont forget to change 'rom' to whatever the program is. Hope that helps...

Unzipping a MUD into the shell - Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Shell Accounts	fatemud	MUD Coding	0	09-19-2006 06:40 PM
2 Free Shell Accounts To A Good Home	fatemud	MUD Administration	0	10-13-2005 09:47 AM
Shell for use	Terron	Advertising for Staff	0	07-26-2004 12:17 AM
shell scripting	Emit	MUD Coding	3	05-26-2002 02:48 PM

04-11-2006, 10:45 AM	#1
NotL337 Member Join Date: Apr 2006 Posts: 42

04-11-2006, 10:56 AM	#2
Baram Member Join Date: Jan 2006 Location: Seoul Home MUD: Tears of Polaris Posts: 218	Sounds like you might need to learn a bit about Linux commands before getting too far into it. man unzip That should give you all the information you need about why unzip isn't working(there are some args you need to supply). As for the make errors, looks like problems in the code, namely that "crypt" isn't defined. Without seeing the code it's talking about, I can't really tell you what the problem is. Disclaimer: Yes, I know I didn't give you/him the answer. You/he clearly stated you/he wanted to learn on your/his own, so I'm just pointing in the right direction.

04-11-2006, 11:21 AM	#3
NotL337 Member Join Date: Apr 2006 Posts: 42	No, thanks--that was indeed quite helpful. The server just went down, but when it comes back up I'll give it a whirl. Although any help with the changing ports thing would also be appreciated.

04-11-2006, 11:25 AM	#4
Baram Member Join Date: Jan 2006 Location: Seoul Home MUD: Tears of Polaris Posts: 218	I don't know that code base, but my guess would be there is a config file somewhere. Probably somewhere near the lowest level directory of the code.

04-12-2006, 12:12 AM	#5
Davairus Member Join Date: Jun 2002 Posts: 159	1) crypt problem I'd suggest start there.. make sure you have the latest and greatest version of smaug of course, there are versions out with all the bugs fixed. Also search that forum for crypt as its been done to death there. I found a lot of answers. 2) setting port Here is a startup script I found for rom a long time ago, smaug is a diku derivative so it should work for you. You'll probably recognise the author. The name of the file is 'startup' and you put it in the area directory. Then to start the mud just nagivate there and type startup. [code] #!/bin/csh # Written by Furey. # With additions from Tony and Alander. # Set the port number. set port = 9000 if ( "$1" != "" ) set port="$1" # Change to area directory. cd ../area # Set limits. if ( -e shutdown.txt ) rm -f shutdown.txt while ( 1 ) # If you want to have logs in a different directory, # change the 'set logfile' line to reflect the directory name. set index = 1000 while ( 1 ) set logfile = ../log/$index.log if ( ! -e $logfile ) break @ index++ end # Run rom. ../src/rom $port >&! $logfile # Restart, giving old connections a chance to die. if ( -e shutdown.txt ) then rm -f shutdown.txt exit 0 endif sleep 15 end [/quote] dont forget to change 'rom' to whatever the program is. Hope that helps...

MUD Coding

Unzipping a MUD into the shell