in reply to psexec and PERL

I am not familiar with how you're remotely accessing your system, but if it's autoflushing your searching for, look no further than the documentation for $| in perlvar:
use IO::Handle; STDOUT->autoflush(1);
(This is documented in perlvar because you can achieve the same effect by setting $|).

In fact, the blurb seems to apply directly to you, albeit in a more UNIXy context:

If set to nonzero, forces a flush right away and after every write or print on the currently selected output channel. Default is 0 (regardless of whether the channel is really buffered by the system or not; $| tells you only whether you've asked Perl explicitly to flush after each write). STDOUT will typically be line buffered if output is to the terminal and block buffered otherwise. Setting this variable is useful primarily when you are outputting to a pipe or socket, such as when you are running a Perl program under rsh and want to see the output as it's happening. This has no effect on input buffering. See getc in the perlfunc manpage for that. (Mnemonic: when you want your pipes to be piping hot.)

If you have the Perl Cookbook ("Ram"), you can check Recipe 7.12. for an example. Hope this helps.

Replies are listed 'Best First'.
Re^2: psexec and PERL
by Anonymous Monk on Feb 17, 2005 at 04:21 UTC
    Thanks, for the Autoflush infomration, I tried that this morning and it had no impact on the program. Continued to misbehave. I was able to run a few more test and determine it was in the "psexec" program that I was using for the remote connection. It was coming into the system in a way not compatable with AS Perl. If you know the oddities of windows and the almost STDIN and STDOUT it offers, then you have a good idea why it didn't work. Anyway, moved on to plan B. I'm running the interactive scripts on a citrix server. :) a little over kill, but why not.