Thanks for the response.
> Make sure that the process (the mud) is being run by an account that has
> write permissions to your lib/ directory. I had this problem when I used
Currently, my permissions are read/write-able by the user/group wart.wart
which is what the autorun is running as (according to ps and it is also what
I launch it as).
> Another thing to look at is that your mud may be hitting an infinite loop.
It isn't hitting an infinite loop because I can definately find the line
of source code that is breaking it. Under normal circumstances this would
produce a core.
I'm very confused over-all why my core went away. I did go from a libc5
to a glibc system, if this offers any hints.
Peter
+------------------------------------------------------------+
| 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/15/00 PST