Simple, yet extremely effective server monitoring tool. Provides a way for the administrator to have their module automatically restarted without manual intervention. PROs: DOES NOT require the administrator to 'click' START to load the module. DOES NOT require ANY additional software to be installed/downloaded (like .NET framework) Provides Audio Alerts should the user desire them, whenever the module is detected as crashed/not responding. Provides user setting for intervals between checks for the module. Proven effective in providing multiple servers over 280 hours straight uptime. Proven effective in minimizing any crashed/Not responding NWServer downtime, with automated restart. Includes Memory freeing utility to reduce or eliminate the Bioware Memory leaks, runs once per hour. This will help minimize or eliminate the Bioware memory leak. (Proven runtimes on 'Tegel Village' averages 200+ hours - that's over 8 days!)
Alright Im in a similar position, and those instructions just went right over my head. Being someone whos done nothing with servers, and only knows basic .ini commands, what do you mean by batch files, putting everything on one line, meh?! You sent those links, but what do we actually do with them? Foolish perhaps, but has it got something to do with just adding options such as "Module=Etc" to the .ini of the nwserver?
Posted by ack ( ..xxx.xxx ) at 2004-04-01 01:49:00
I like the simplicity of the program but how do I make it work? I can auto-start a server with it no problem, but I cant figure out for the life of me how to get it to start a module. Could someone tell me what to do if i wanted it to start a module called Daleland?
Site
at 2005-08-25 18:44:25
