Discussion :

[Jxxx7]

Bonjour,

Je crée un script d'automatisation et je suis contraint de passer par Telnet même si je n'approuve pas, mais bref, là n'est pas la question.

Dans mon script, après m'être connecté en Telnet sur le serveur et avoir lancé un 'ls' pour voir la liste de mes répertoires, j'ai des caractères bizarres à l'écran et j'aimerai savoir comment voir correctement mon résultat.

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
3
4
5
6
use Net::Telnet;
$telnet = new Net::Telnet ( Timeout=>10, Errmode=>'die');
$telnet->open($ARGV[0]);
$telnet->login($ARGV[1], $ARGV[2]);
print $telnet->cmd('cd /volume1/');
print $telnet->cmd('ls -1 | grep jeu');

Avez-vous ZE commande?

Merci

[Philou67430]

Lu dans la notice de Net::Telnet :

Connecting to a Remote MS-Windows Machine

By default MS-Windows doesn't come with a TELNET server. However third party TELNET servers are available. Unfortunately many of these servers falsely claim to be a TELNET server. This is especially true of the so-called "Microsoft Telnet Server" that comes installed with some newer versions MS-Windows.

When a TELNET server first accepts a connection, it must use the ASCII control characters carriage-return and line-feed to start a new line (see RFC854). A server like the "Microsoft Telnet Server" that doesn't do this, isn't a TELNET server. These servers send ANSI terminal escape sequences to position to a column on a subsequent line and to even position while writing characters that are adjacent to each other. Worse, when sending output these servers resend previously sent command output in a misguided attempt to display an entire terminal screen.

Connecting Net::Telnet to one of these false TELNET servers makes your job of parsing command output very difficult. It's better to replace a false TELNET server with a real TELNET server. The better TELNET servers for MS-Windows allow you to avoid the ANSI escapes by turning off something some of them call console mode.