Hi. I had the same problem when reading rapidly changing files over NFS. It seems that writev() in Linux 2.4.x issues a SIGBUS if NFS reports a bus-error, although write() does not.
This issue has not been fixed in the upstream version 2.25b and it seems Jef Poskanzer no longer activively maintains it. As a workaround I added a new signal-handler for SIGBUS, which just logs the signal and rolls forward. Patch for 2.25b: http://dev.avoltus.com/villeja/thttpd-2.25b-sigbus.patch Patch for 2.23-beta1 (Debian/Sarge): http://dev.avoltus.com/villeja/thttpd-2.23beta1-sigbus.patch -Ville -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
