title: lighttpd, fastcgi and application script written in "C" using libfcgi - Weird system error message
body: <p>I get a wierd Linux system message "Transport Endpoint is not connected" in response to a write call  immediately after a successful open call. All this happens immediately after a Slackware Linux 2.6.33.4 reboot.</p>
  
  <p>I'm writing a forms-handler in C and it runs under lighttpd and fastcgi (and before some smart alec pipes up and asks 'why am I not using his/her favourite language, it's because I like C --- OK? OK!).</p>
  
  <p>I've got the major facilities of the application running - it displays index.htm (which is a form) and when the form is 'Submit'ted, finds the program I've written which correctly processes the contents returned and displays the next form.  It's got complex enough that now I need to print some debugging statements somewhere, to give me some feedback from program additions. Thus arises the problem.</p>
  
  <p>Research indicates that this message usually means that the endpoint of the file path is not or has become not mounted but /tmp/debug.log (which is the file I'm trying to create/append-to lives on the root partition. But then why is the open() successful but the write() is not?</p>
  
  <p>The program fragment below is the bit which is giving trouble. The printf() statements send output to the web interface (for those unfamiliar with libfcgi) to give me some idea what's happening.</p>
  
  <p>I can't get my (properly indented) code through this forum's demented code filter and I can't attach it in a zip file, so you'll just have to take my word that the syntax is correct.</p>
  
  <p>Any clues?</p>