C H A N G I F A Q
Error messages |
||
Message File Not Found | What is the meaning of message file not found? |
The development tool VisualAge C++, used to create Changi, requires
to separately bind runtime messages to executables unless you got
DDE4.MSG on your disk. On development machines, where VisualAge is
installed, this file is available and so it was overlooked to
bind the runtime messages to Changi before shipping some previous
versions.
DDE4.MSG can't be distributed with Changi, because it's copyright protected. |
Can't find noop | How to interpret the messages 'nntpd: Can't find noop' that syslog gives when running Changi. | Certain newsreaders request a newsgroup named noop. This problem hasn't been tracked down yet and needs further investigation. However, it doesn't seem to hurt. |
Error 640 | I recently saw regular entries in my syslogd like this: Error 640 (DosRequestMutexSem 30240) |
As a multithreaded application, Changi uses several semaphores
for mutual exclusion while accessing shared resources. In the
past there had been several reports about failures during
semaphore requests. Although these errors look similar, their
cause isn't.
That's the background. 30240 refers to the specific routine, at which the semaphore access failed, 640 is the error code for timeout. Putting it together shows, that Changi fails with timeout (30 seconds) in a procedure named flush_dircache. All routines using this semaphore look quite simple and are most probably free of bugs. However, they make extensive use of dynamic memory allocation and may fail in case of heap memory corruption introduced by any other part of Changi. As a result of this somewhat lengthy explanations, it seems to be most difficult to find the cause of this problem. Either you may discover another syslog line with any, on the first look unrelated problem - or we may discover similar configuration items among two or more people with this problem. |
Return to the main FAQ page.