>So what might fix this odd problem? Basically, it appears that fake
>connects are attempted, and it causes major lag on the program, including
>causing the CPU resource time to shoot way up (after 24 hours of running,
>the MUD uses less than 1 minute of CPU time at most. When the fake
>connects are attempted, it uses practically 80% of the CPU time! Within
>2 minutes the CPU time is well over a minute and a half).
Well, unless I am mistaken, the reason for this is that the MUD is trying
to resolve the hostname. And since there is no IP of that number, it
can't get a host name, and as such, has to time out. There are a few
things you can do if that is the problem. #1., get the asyncrynous name
resolver from the site. or #2. Turn slow NS on, then it won't resolve
the hostnames. Maybe you can even try and use it to track them down.
Good luck, those sick people (probably friends with those sending junk
e-mails) should be dragged out into the street and shot.
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/08/00 PST