Prez Bush

I understand that terminating the window isn't the same as killing the process but the two usually go hand in hand. If I start dedicated server and then close the window, the process goes. If I wait two days and 200mb of ram later, the process hangs. Anyone have any ideas on automatically terminating the server and restarting it on a daily basis? That would be a sufficient workaround ( I think, assuming the process dies) until the leak issue is addressed.

I run a dedicated server on Win2k Server with 512mb ram and a T3 connection. Win2k is as patched as a Microsoft OS can get but I find that the server slowly grabs more memory until it quits running. This takes about 2 or 3 days of 24/7 running. When I kill the window to get it to restart (running in a .bat, perm loop) it kills the window but not the process as seen in task manager. That process starts out using ~24mb of ram and has over 100mb when I force kill the process. After forcing the process down, I can restart the dedicated server engine and the whole loop begins again. I have tried rebooting the whole server too. There isn't anything running on this server but OFP. On another note, why can't people join an in progress game like most other first person shooters out there? (with exception of Rainbow Sick)