You have an old (broken/incomplete) config.cache (config.status) file left over. Delete those! Or if you have a recent set of the auto* tools installed (See INSTALL.html) run the CVSMake script, and then configure again. configure (and the generated Makefiles) won't work if the build directory resides in a path which has embedded blanks, e.g. "/usr/work/Fine Software". The simple and only solution is to move it to another path.

Your httptunnel connection has failed on the client end (possibly due to network congestion), but the server end has not recognized that the connection has been lost and won't allow another connection until the first connection times out. To establish a more stable tunnel, try experimenting with the various options for the htc and hts programs.

When I spawned a process using Expect, I got the following message: parent: sync byte read: bad file number child: sync byte write: bad file number This is one of these "should not happen" errors. For example, the following question in this FAQ mentions that it could be the fault of the C library. Another possibility is that you've run out of some system resource (file descriptors). The most likely reason is that you're calling spawn in a loop and have neglected to call close and wait.

Lots of people have reported the following error from Expect on RedHat 5.0: failed to get controlling terminal using TIOCSCTTY parent sync byte write: broken pipe Martin Bly reports that: The fault is/was in the GNU libc (aka glibc) provided by Red Hat Software. Our sysadmin updated the version of the C libraries we have installed and both problems have vanished - in the case of the expect test, without a rebuild.

People have reported the following error from Expect on RedHat 5.2 when using cron: failed to get controlling terminal using TIOCSCTTY parent sync byte write: broken pipe I have no idea, however I've received two workarounds: From: patrick_scannell@mail.fws.gov >I found that the script runs fine as an at job. So I just have cron >schedule the at job and everything works. I don't understand it, but >I'm happy. From: "Charles Hays" <charles@dialus.

Most common reason of treatment failure is the failure to observe drug administration, which commonly results in treatment failure.

If you use Sandboxie with the GreenBorder Online Test, the test will probably report that Sandboxie has failed, because the test was able to copy files from the My Documents folder to a folder on the desktop named Stolen Files. First, the default Sandboxie settings do not block any files from being read, and this includes the files in My Documents. But see ClosedFilePath for more information.

You configure each section (numbered 1-10) by pointing DSpy to the proper directory on your network. By putting a shortcut to DSpy in your startup folder, it will start with your TSC client during every boot/login and automatically start tracking your TSC progress.

From: libes (Don Libes) To: morton@hendrix.jci.tju.edu (Dan Morton) Subject: Re: Sorry to bother you, but... Dan Morton writes: >Don, > >I've posted an inquiry to comp.lang.tcl about my configure problems with >expect, but I've not yet gotten a reply. Perhaps you can nudge me in the >right direction? > >I'm running HP-UX 9.0 on a 735, and I've snagged the latest versions of Tcl >and expect from NIST (7.4 and 5.18 respectively). My gcc is v2.6.

From: libes (Don Libes) To: wren@io.nosc.mil Subject: Compile fails with: Don't know how to make pty_.c > I'm trying to compile Expect on hpux 9.01, > downloaded from ftp.cme.nist.gov expect.tar > after running config > the make fails with "Don't know how to make pty_.c. (compile fails) > I see three versions pty_sgttyb.c, pty_termios.c and pty_unicos.c in > the load, but the configure picked none of them. > I tried forcing to pty_termios.

From: libes (Don Libes) To: Will Smith (AC) <william@ritchie.acomp.usf.edu> Subject: Expect Will Smith (AC) writes: >Hi there. I was wondering if you had any ideas to why i am getting >this problem running an Expect script which tries to spawn a talk >process to myself on another machine. Would it have anything to do >with the fact that the executables are NOT installed in /usr/local/bin >or because it wasnt installed by ROOT or what.

It means just what it says: the server was expecting a complete set of HTTP headers (one or more followed by a blank line), and didn't get them. The most common cause of this problem is the script dying before sending the complete set of headers, or possibly any at all, to the server. To see if this is the case, try running the script standalone from an interactive session, rather than as a script under the server.

Did you unpack the Cocoon distribution with tar? It seems like "tar" is broken on macosx, you need to use "gnutar" instead to unpack the Cocoon distribution archive. See this message.

Several factors contribute to the failure of composite wood siding: the performace of the product itself, the quality of its installation, and/or the design of the sturcture. Composite siding does not handle water very well. Water droplets collect on the bottom edge of the siding after a rain shower or morning dew. The wood fibers expand and contract causing the boards to crack, buckle, peel and delaminate. As the paint cracks it allows more moisture and damage to occur.

The hardware check is not foolproof and might not work correctly for all hardware. USB devices and copy-protected media in drives may interfere with the check. If the check fails, disconnect all USB devices (USB drives including mp3-players such as iPod, USB card-readers etc.) and remove all media from disk drives and try again.

The capacity used by BT for SatStar Africa is non pre-emptible and fully restorable. This means that if the transponder should fail, an alternative will be provided on the same satellite. Should the satellite fail, the service will be relocated to an alternative satellite where possible.

JSA: The main reason for failure of a leach field is plugging caused by a failed septic tank. Particles of non-decomposed septic material escape the septic tank outlet baffle and decrease the porous nature of the leach field earth. Over time the effluent water may seek relief by bubbling up to the surface since it no longer can be absorbed properly downward into the ground. Offensive odors and dangerous bacteria in the surface water can be identified.

The fail safe is an electronic device that plugs between the throttle servo and the receiver. It senses voltage and frequency changes or signal loss. In other words, if your battery drops to a specific voltage that could cause loss of signal to the radio or if you lose signal between the transmitter and the receiver, it shuts the throttle to a preset position, usually idle, preventing runaways.