in reply to Re^8: Threads Printing Issue - Output Mangled / Term Crashing
in thread Threads Printing Issue - Output Mangled / Term Crashing
strace -o /tmp/out -f perl -e 'print `ssh localhost -tt -l root tcpdum +p -c10 -nntttt`'
On my computer that works pretty fine, and I don't see any tty access. Maybe just updating the ssh client could solve your problem.
update: Ah, I can see what's happening:
ssh -tt ... reads the terminal flags from STDIN (ioctl(0, TCGETS, ...)), sets new ones (ioctl(0, TCSETSW,, ...)) and runs the remote command. Then, upon exit, it restores the original flags.
The issue is that with multiple ssh processes running in parallel, some of them may read the already modified flags and so later, reset STDIN to an incorrect state.
An easy workaround is to wrap the part of the code where the threads are started and then joined with an extra couple of TCGETS/TCSETSW ioctl calls. Another option is to just redirect STDIN from /dev/null.
update 2: The following program works correctly on my computer:
use strict; use warnings; use threads; use threads::shared; my @threads; my @servers = (('localhost') x 100); my $lock:shared; foreach my $server (@servers) { chomp $server; push (@threads, threads->create (\&dumpServer, $server)); } foreach (@threads) { $_->join(); } sub dumpServer { my $server = shift; my $net = `ssh -l root -tt $server '/usr/sbin/tcpdump -c10 -nntttt 2 +>&1' </dev/null`; lock($lock); print "TEST - $server\n$net\n\n"; }
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^10: Threads Printing Issue - Output Mangled / Term Crashing
by bigbot (Beadle) on Apr 16, 2014 at 08:01 UTC | |
|
Re^10: Threads Printing Issue - Output Mangled / Term Crashing
by bigbot (Beadle) on Apr 18, 2014 at 01:02 UTC | |
by salva (Canon) on Apr 19, 2014 at 19:43 UTC | |
by bigbot (Beadle) on Apr 22, 2014 at 09:55 UTC |