Re: problem with fnord-1.9 and wget

Thus spake Thilo Bangert ([email protected]):
> > Can fnord read the contents of the file it's supposed to send out?
> It sure can. In fact many other connections are served fine.

> Looking at the attached trace I would assume, something weird happening in 
> sendfile, but i am no expert on this.

This trace looks better than the one you sent me earlier, because
setsockopt no longer fails with ENOSOCK.

However, it shows that sendfile64 is called with the wrong length.
Since fnord calls it with the right length when compiled with dietlibc,
I assume this is a header problem.  I just compiled fnord with glibc and
it also uses the right length for my test file.

This is quite mysterious.  Please make sure your strace is the correct
version.

Just to make sure we are using the same code base: please make sure you
use the current CVS version.

> BTW - is there supposed to be a copy of /etc/localtime in the chroot ?

No.  It's a glibc issue that it's being opened in the first place.

Felix