Re: Capturing stdout.

1999-09-21 Thread Juergen Kreileder
> Neil Clayton writes: Neil> Oh, thought I would provide an explanation of my problem, Neil> just so people know. Neil> The full command was: Neil> sflwl -hlwl.fourmilab.ch:2076 '[EMAIL PROTECTED]' Neil> So this must mean that the VM does not use the *nix shell in

Capturing stdout.

1999-09-21 Thread Neil Clayton
Oh, thought I would provide an explanation of my problem, just so people know. The full command was: sflwl -hlwl.fourmilab.ch:2076 '[EMAIL PROTECTED]' The argument to sflwl being 1. -hlwl.fourmilab.ch:2076 2. [EMAIL PROTECTED] Which of course works fine in the shell. However; I was us

Re: Fixed (capturing stdout)

1999-09-21 Thread Todd Papaioannou
At 20:52 21/09/99 +1200, Neil Clayton wrote: >Well, sorry to leave so many messages regarding this. >I've worked it out - so problem is now history, and it was nothing to do >with the VM. And the fix was...? cheers Todd --- To

Fixed (capturing stdout)

1999-09-21 Thread Neil Clayton
Well, sorry to leave so many messages regarding this. I've worked it out - so problem is now history, and it was nothing to do with the VM. Cheers, Neil Clayton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "u

More info on capturing stdout

1999-09-20 Thread Neil Clayton
Following up on my previous message, I have more information: I've been playing with the code for sflwl, and found that something *very weird* if happening. This is a snippet from lwl.c. myPrintf("While\n"); while (sdes_count-- > 0) { struct l