On Sunday 06 November 2005 22:02, Carlos E. R. wrote:
The Monday 2005-11-07 at 12:59 +1100, scsijon wrote:
6 Nov 15:19:31 ntpd[1013]: sendto(129.177.13.13): Bad file descriptor
Weird! I did not expect that. I had a look at the source code, but I get no clue what it can _really_ mean. And the documentations does not mention that error, I grepped for it.
/cut
If it was windows i'd say it was trying to send a filename of a length not acceptable to send (too long). Alternately are you trying to send a filename with an unacceptable character in the name (there are a few such as the Null)? Many firewalls and ISP's won't pass these as they allow filehiding.
We are talking of the ntpd clock update protocol and daemon. The OP is not sending any file at all, and we have no idea what file the log is referring to.
It's not sending a file per se. It's sending (writing) and receiving (reading) a stream of bytes in the protocol for ntp. If the code snippet posted earlier is the correct place the "Bad file descriptor" message is being generated, then the program (the ntp client) appears to have failed to send a message to the remote server. I would have to see more of the code to see what triggered the EBADF. The way it looks is it implies that the initial socket setup wasn't successful. More code equals less guessing. I don't have the code for ntp handy.