I have just joined this list, so I am unsure of protocol or what has been discussed before. Forgive me if I offend anyone with this post. I have 3.0 Patch Level 7 and I want to initiate the CPU Monitoring capabilities. Another system manager I know is interested in knowing how much strain a MUD puts on a system. He is deciding whether to allow one or not. When I added #define RUSAGE to comm.c as the docs describe, my code will not compile. I am placing the line right after the #define __COMM_C__ Am I doing something wrong, or is this a bug existing within Circle 3.0 patch level 7? If it is a bug, I wish to report it. Or, is there a different procedure for initiating CPU monitoring? Also, from all of your personal experiences...how much strain does a mud put on a system? Is it noticable? Does it really slow down internet actions? thomas knight@forest.fnr.purdue.edu
This archive was generated by hypermail 2b30 : 12/07/00 PST