[Home] [Downloads] [Search] [Help/forum]

Gammon Software Solutions forum

See www.mushclient.com/spam for dealing with forum spam. Please read the MUSHclient FAQ!

[Folder]  Entire forum
-> [Folder]  SMAUG
. -> [Folder]  Running the server
. . -> [Subject]  a question
Home  |  Users  |  Search  |  FAQ
Username:
Register forum user name
Password:
Forgotten password?
(New message)
Subject: a question
Name:
Your forum user name.
Register forum user name
Password:
Your forum password.
Forgotten password?
Message:
Message to be posted (in English, please)
Maximum of 6000 characters. Text only please, no HTML.
Forum codes:
Check this if your message uses 'forum codes' or templates (auto-detected for new posts).
Forum codes Templates

Save this message ...

Subject review (reverse sequence)

Posted by Nick Gammon   Australia  (18,770 posts)  [Biography] bio   Forum Administrator
Date Wed 09 Jun 2004 01:36 AM (UTC)  [ quote  ]
Message
First, don't panic! ;)

The only way it is likely to "fill up a drive" is if the log file is written to with a great deal of information.

Normally your "startup" script would write to a log file. You could view that by using "tail". Using the -f option (follow) lets you view the data as it is written.

So, say you typed:

tail -f log/mylog.txt

and you saw heaps of things being written, much more than you expect, then you need to kill the process. One way of doing this is to use "ps" to find the process ID, like this:


$ ps aux | grep smaug

nick     30181  0.0  0.8  7584 5424 pts/1    S    07:28   0:00 ../src/smaug
nick     30430  0.0  0.0  3576  632 pts/3    S    11:07   0:00 grep smaug


In this case I am taking the output from "ps" and piping it through grep to narrow it down to the "smaug" entries. One of them (process ID 30430) is the grep command itself, so it follows that the other one (process ID 30181) is the actual SMAUG game (which you can see is running ../src/smaug).

Then type:

kill -9 30181

This kills process 30181 immediately. Then you would investigate why it is in the loop. If it isn't obvious you might use gdb rather than killing it. See my write-up on using gdb elsewhere on this site. In this case you would need to "attach" gdb to that process, eg.

gdb ../src/smaug 30181

Then type Ctrl+C to break into the running process and "bt" to get a backtrace, to see where the loop is.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
[Go to top] top
Posted by Ithildin   USA  (262 posts)  [Biography] bio
Date Tue 08 Jun 2004 10:06 PM (UTC)  [ quote  ]
Message
Ok, i'm looking into putting my mud on a server and i've been looking at different ones and such and looking at FAQs. i found this and i want to make sure on how exactly it starts and how i would stop if it happens.

Quote:

New admins generally
don't know how to keep tabs on a MUD, and often times will start the mud, see that it gets
stuck into a loop, panic, and log out, leaving the game to fill up the entire drive.


what would i need to do if this happens and how does it start?

Thanks,
Ithildin
[Go to top] top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.

2,624 views.

[Reply to this subject]  Reply to this subject   [New subject]  Start a new subject   [Refresh] Refresh page

Go to topic:           Search the forum

[Go to top] top

[Home]

Written by Nick Gammon - 5K

Comments to: Gammon Software support
[RH click to get RSS URL] Forum RSS feed ( http://www.gammon.com.au/rss/forum.xml )

[Best viewed with any browser - 2K]    [Internet Contents Rating Association (ICRA) - 2K]    [Web site powered by FutureQuest.Net]