Restarting Dynamic Zone After a Crash?

**trevius** · #1 05-01-2008, 05:11 PM

Sure, Andrew80k. I would love to see what you have setup. Only having 1 example makes it hard for me to understand what is happening, and what needs to be there or not.

I would be especially interested in something that wraps log files after they reach maybe 250k or so if that is at all possible. I have no need for a 500MB log file lol. Heck, I wouldn't even mind a script that turns off the log files completely.

**trevius** · #2 05-02-2008, 12:48 AM

What the heck are these core.<number> files that are filling my hard drive? I already have a couple GB worth after less than 1 day of having the server up!

**AndMetal** · #3 05-02-2008, 02:07 AM

Quote:

Originally Posted by trevius

I would be especially interested in something that wraps log files after they reach maybe 250k or so if that is at all possible. I have no need for a 500MB log file lol. Heck, I wouldn't even mind a script that turns off the log files completely.

The easiest way to not output a log file is to redirect to /dev/null. I'm not sure of the best way to do this for the zone files (maybe a symbolic link to /dev/null?), but here is an example for the world server log that is made in your startup script:
Change

Code:

./persist_world 2>&1 > logs/world &

to

Code:

./persist_world 2>&1 > /dev/null &

Quote:

Originally Posted by trevius

What the heck are these core.<number> files that are filling my hard drive? I already have a couple GB worth after less than 1 day of having the server up!

Those are basically debug files. They are enabled with the -pg switch in the makefiles for eqlaunch & zone. I made brief mention of it in the Wiki, but at the time I wrote that part, I didn't know that's what created them. Basically, change the lines in eqlaunch/makefile and zone/makefile that begin with COPTS to remove the -pg.

**trevius** · #4 05-02-2008, 02:47 AM

Weird, I know for sure that I removed them before my compile. I followed your wiki exactly. I've gone through it 2 times now (rebuilt 2 times), and I am going to do it again soon for another PC. I just checked the source I used and -pg is definitely removed. Not sure why it makes these core files, but I don't think it is good for my server load and the amount of data growing that fast is insane. I probably had 20 100MB files in less than 1 day.

**AndMetal** · #5 05-02-2008, 02:04 PM

Apparently I'm retarded and I have no idea what I'm talking about.

However, after searching around teh Interwebs a little bit, I remembered the core.whatever files have to do with the following line in the startup script:

Code:

ulimit -c 99999999

In my script, I just commented it out (with a #), and I no longer get the core files, which definitely eat up a lot of space relatively quickly.

Aramid · #6 05-02-2008, 07:31 PM

I may be wrong, but it seems my setup made core files after a crash. It seems they are like dump files used to debug the crash, but I could be completely wrong here, this is just a guess on my part.
I do have the unlimit -c 999999 in my startup as well, so I will remove it and see what happens....

**trevius** · #7 05-03-2008, 12:59 AM

Makes sense lol. Thanks AndMetal! And ya, they do show up after a crash. That normally wouldn't be a huge issue, but I was still running my zone resetters in all of my custom zones, so essentially it thought I had 20 zone crashes per day and kicked out a 100MB file each time.

I have no use for those files anyway. They are too huge for me to open them with an editor and I have no idea what I would grep for in them. I will definitely be commenting that out!

Thanks guys. This info is really helping me get things setup nicely.