From: Chris M. <mut...@mc...> - 2003-09-15 19:12:10
|
Yes. I used that extensively when debugging the program that the fragment= in my original post came from. However, in this case, the script works perfectly when= running on the terminal and I can see the output of that ($Expect::Exp_Internal=3D1;), but when the script is= daemonized, there is no connection to the terminal to send output to. Note that in the fragment in my original post, I 'close STDOUT;'. I even tried something like the following. close STDOUT; open (STDOUT, "> log_file"); print "Hello, World!\n"; That worked. I was able to use standard print statements (that print to= STDOUT by default) to send stuff to the file, but any output from expect did not show up in= the file. I tried that again just now to be sure. I even tried opening STDERR to a= file. In both cases the program now hangs with a 0 length output file. It does not even say that it did not get the prompt. I know that is hung= as it showed up in `ps -eaf` for a longer time than any of its timeouts. Thanks for the idea though :-) -Chris Muth On 9/15/03 at 12:24 PM John Mahoney wrote: > >Have you tried setting > $Expect::Exp_Internal=3D1; >before creating your expect object? > >This will produce a lot of debugging info that may help >you locate the cause of your trouble. > >-- >John >_________________________________________________________ >John Mahoney |