If you read the docs for Net::Telnet again, you'll see that it says that "If the command happens to return no output, a list containing one element, the empty string is returned." I'm not 100% sure that Windows 2000 Advanced Server behaves the same way (as every other version of Windows that I have ever run) but in my experience mkdir only displays text where there was a problem. If the mkdir command was successful, @df would would contain one empty string.
By the way, I've never tried to use dump_log from within a die. The docs for Net::Telnet say that "This method starts or stops dump format logging of all the object's input and output." This doesn't sound like something you would want to do in a die. I've also never used dump_log the way that you are attempting to (dump_log=>$dumpfile). (Without testing) I would say that your dies will output to STDERR something very similar to "dump_logstorage_dumpfile.txt at C:\path\to\file.pl line XXX." It would make more sense to turn on dump_log right after the connection is made and to die with the last error reported (die($storage_telnet->errmsg)).
In reply to Re: Capturing Telnet Command Outputs on Windows 2000 machines
by Mr. Muskrat
in thread Capturing Telnet Command Outputs on Windows 2000 machines
by auyong
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |