10 May, 2009, boblinski wrote in the 1st comment:
Votes: 0
Quote
Sun May 10 19:11:02 2009 :: Sock.sinaddr: 127.0.0.1
Sun May 10 21:40:18 2009 :: EOF encountered on read.
Sun May 10 21:40:18 2009 :: EOF encountered on read.
Sun May 10 21:40:18 2009 :: EOF encountered on read.


What does this mean and how do I fix it?
10 May, 2009, Malek Kervanes wrote in the 2nd comment:
Votes: 0
it means it was expected to find more information in a file you were trying to load and it found the end of the file instead.

how to fix it…well, can't figure that out until we see what's causing the error.
10 May, 2009, Kline wrote in the 3rd comment:
Votes: 0
Usually this is a client connecting to the game, sending no data, then disconnecting.
11 May, 2009, quixadhal wrote in the 4th comment:
Votes: 0
I would grep through your source to find that exact string "EOF encountered on read.", and add a bit more useful debugging information… such as the name of the function, and if it's a file rather than a socket, the filename that was being accessed.

It might be anything from a socket error to a corrupt player file.
11 May, 2009, boblinski wrote in the 5th comment:
Votes: 0
The only place "EOF encountered on read." is found is:

comm.c in bool read_from_descriptor (DESCRIPTOR_DATA * d)

This is the section of code:

#if defined(MSDOS) || defined(unix)
for (;;)
{
int nRead;

nRead = read (d->descriptor, d->inbuf + iStart,
sizeof (d->inbuf) - 10 - iStart);
if (nRead > 0)
{
iStart += nRead;
if (d->inbuf[iStart - 1] == '\n' || d->inbuf[iStart - 1] == '\r')
break;
}
else if (nRead == 0)
{
log_string ("EOF encountered on read.");
return FALSE;
}
else if (errno == EWOULDBLOCK)
break;
else
{
perror ("Read_from_descriptor");
return FALSE;
}
}
#endif
11 May, 2009, Banner wrote in the 6th comment:
Votes: 0
Kline said:
Usually this is a client connecting to the game, sending no data, then disconnecting.

Kline is right. Nothing to worry about. At least on my MUD, it means someone disconnected at the logon screen or closed their mud client while ingame.
11 May, 2009, JohnnyStarr wrote in the 7th comment:
Votes: 0
I've had the same issue before. It might be noted that because a socket descriptor uses
I/O, EOF has to do with what the socket is 'reading', not a P-file or Area-file.
0.0/7