Hey!

I'm running LdMUD 3.2.7 and a modified version of the really old NannyMUD export lib. Running it just for fun, to tinker with and learn coding. Now... A real strange problem have occured recently.

Idle time, combat heartbeat, age and uptime counting (among some of the things I have noticed) dont work anymore. You are always 0 seconds idle. You dont grow in age. Uptime of the mud is stuck at 3 seconds. If you go ld, then you never get kicked out of the mud, you are eternally linkdead.

I have looked and looked, but cant find anything that seems to be wrong. I am fairly sure it is a lib problem cause an older version of the lib works perfectly. But my dumb brother erased it... So I need to debug this. Anyone who got any idea at all what the problem might be?

/F451

I would suggest that the problem is with the driver, or rather, the mis-match of the old NannyMUD lib and the LDMUD driver. For example, the query_idle() efun, which is needed for the idle time, might be missing, do nothing, or do something different that the one in the old NannyMOS originally running the lib.

You will have to check the driver source to see what you should be using, and then modify the lib. Or, you could implement the needed efuns (or change behaviour of existing ones).

Good luck.

Thanks! I'll start working on it now that exams are over.

I am still there. Hard to abandon the old homemud. Besides, this is just a learning project of mine. Something to tinker with.

I have now tried all my old backups and the error remains. Before reinstalling a new backup, I have wiped the old one.

So I am starting to think that the guy who have given me a bit of server space maybe have done something with his server. Not that I really know if some sort of server setting can create this error. But... Since this bug didnt exist when I shutted down the mud for the exam period, but it exist now... What else could make the mud bug like that while being down?

I get a 'exec of erq demon failed.' when I start the driver. Think that is any related? Sometime I also get that it expects 0 but got 9.

Another totally weird thing is the uptime. First times, uptime was 3 seconds. Period. Now... After I reinstalled the driver, uptime started at 1. And then it increases by one for every time I start the parser.

Update: Ok, it really must be a problem with the server. I tried installing the mud on another friends linux computer. Worked perfectly. Still same error on the server though. Any clues what could be up with the server then? The owner says he just moved a couple of directories in the scout account over the last 6 months, that he can remember.

I made it work! The server admin had no idea what to do... He was tinkering and trying, same with his self labeled linux guru friends.

I noticed uptime of the server was over 300 days and figured maybe something happend over new years. I convinced them to reboot and now it works! *flex*

Thanks for the help though.