28 Apr, 2009, boblinski wrote in the 41st comment:
Votes: 0
I'm using ISUnlimited and am connecting using putty…

Still having trouble using startup script..
$ cd area
$ chmod u+x startup
$ ./startup 8888 &
[3] 23014
28 Apr, 2009, Kline wrote in the 42nd comment:
Votes: 0
What's the problem exactly…?
28 Apr, 2009, boblinski wrote in the 43rd comment:
Votes: 0
It doesn't go through the start-up and say 'rom is ready to rock on port 8888.'
28 Apr, 2009, David Haley wrote in the 44th comment:
Votes: 0
It's probably running in the background – that's what the startup script does for you.
28 Apr, 2009, Malek Kervanes wrote in the 45th comment:
Votes: 0
yeah. Try typing "ps x" and see if it shows up there.
28 Apr, 2009, boblinski wrote in the 46th comment:
Votes: 0
It appears as though you were both right:
$ ps x
22977 ? S 6:42 /bin/csh ./startup 8888
23014 ? S 78:24 /bin/csh ./startup 8888
25655 ? S 0:00 ../src/rom 8888
27634 ? S 0:00 sshd: savagerealm@pts/5
27636 pts/5 Ss 0:00 -bash
27644 ? S 0:00 sleep 10
27645 pts/5 R+ 0:00 ps x

Three questions:

1) What does that list of things mean?

2) How do I shutdown my mud now? (I've tried "shutdown" and "reboot" from my IMM char, but the the mud continues to run)

3) What other commands should I familiarize myself with when it comes to using putty?
28 Apr, 2009, Kline wrote in the 47th comment:
Votes: 0
Your startup script is running twice. Notice how directly below the second instance there is "../src/rom 8888"? That is the second startup script launching your MUD for you. You should kill the first copy of the script with kill -9 <pid>. So, kill -9 22977 to end it.

The line with sshd: is your connection to the server. If you kill it you'll disconnect yourself :). Also below that is your current shell environment, bash. 27644 looks like the sleep routine in your first startup script that pauses it from looping; if you kill the extra copy of your startup script you won't need to worry about that. The last is the command you ran, ps x.

All you really need to know is how to start the MUD (which you know). If shutdown from in-game doesn't work just kill the PID of your MUD, 25655 in this case.
29 Apr, 2009, Banner wrote in the 48th comment:
Votes: 0
Ps ux is more informative, showing each individual process's memory and cpu usage as well.
30 Apr, 2009, boblinski wrote in the 49th comment:
Votes: 0
$ nohup ./startup 8888 &
$ nohup: ignoring input and appending output to `nohup.out'

Is that normal?
30 Apr, 2009, David Haley wrote in the 50th comment:
Votes: 0