Hi again Jon,
Yes - linux server. I didn't think Windows servers even existed outside the corporate environment (not that I'd really know).
Before my previous post, and again this morning, I tried almost exactly what you have just said, except the path is different (as required), and step 3, I used:
php chatd.php --start (as per previous instructions)
(Can anyone please
clear up for me whether that & should be on the end of the code? It seems to make no difference)
This works, but the SSH window needs to stay open or the chat window dies, which sounds like it may be normal. It will hopefully do for now, as I have a scheduled chat session in 1 hour from now, and the 'normal method' was just causing complaints.
However, there are still some odd behaviours. On my machine, I see no user list, but if I hit the 'back' link in that frame, I see the user list. But that only works until the frame refreshes then I lose the list again. My other test user here is seeing the user list just fine.
Also, if I open a second window, to a different chat room, my name/avatar gets added as a second (duplicate) copy of me to the first chat window, and the user list doesn't give the DNS error page, it just stays white. This may or may not be normal - I have no idea - does the chat module allow or prohibit a user being in more than 1 room at a time?
Now, I just went back to check on the chat window again and it has disconnected/died. Is chatd supposed to die if nobody uses it for x minutes, or something? Is there a difference in that behaviour between starting it manually and starting by using the startup file method? Unfortunately I can't just experiment my little heart out with rebooting - there are other clients on this server, and it's not appropriate for me to experiment in case somethign goes wrong.
ANother thought ... would it be possible (or even helpful) to run the chatd off another server (separate from the server moodle is located on)?