Index: [Article Count Order] [Thread]

Date: Tue, 7 Apr 2009 10:51:06 +0900
From: Yukiyo Akisada <akisada@tahi.org>
Subject: [users:01163] Re: Cannot create a new IO::Tty from fd 4: Bad file descriptor
To: swnath@cisco.com
Cc: sudks@cisco.com, dtripati@cisco.com, users@tahi.org
Message-Id: <20090407105106.4475b89a.akisada@tahi.org>
In-Reply-To: <49D4BFD5.000007.03756@SWNATH-WXP>
References: <3f9723c40904020615k6d5b7540hd438e00874da92c3@mail.gmail.com>	<49D4BFD5.000007.03756@SWNATH-WXP>
X-Mail-Count: 01163

Hi, Swaprava.

Which version of FreeBSD are you using?

The newer p5-IO-Tty has the problem.

Please refer to
<http://www.freebsd.org/cgi/query-pr.cgi?pr=128941> or
<http://www.nabble.com/misc-128941:-Perl-module-IO::Pty-no-longer-working-after-upgrading-to-FreeBSD-6.4-PRERELEASE-td20543851.html>.

I hope that these pages will help you.

Thanks,


On Thu, 2 Apr 2009 19:08:29 +0530
"Swaprava Nath" <swnath@cisco.com> wrote:

> Hi all,
> 
> Since my perl scripts were not running properly, I reinstalled the perl
> modules after deinstalling the older version. Now, even the scripts which
> were running with the older version of the perl modules stopped working. The
> error messages are as shown below:
> 
> ========== TEST 1 ==========
> ./LLA_DADSuccess.seq -pkt LLA_SAA.def -log 1.HTML -it "Address
> Autoconfiguration and Duplicate Address Detection"
> Start Capturing Packets (Link0)
> *** Target initialization phase ***
> Wait 15 second
> Cannot create a new IO::Tty from fd 4: Bad file descriptor at
> /usr/local/lib/perl5/site_perl/5.8.8/V6evalRemote.pm line 582
> reboot_async.rmt returned status 9
> *** Target testing phase ***
> ==========================
> ===================================
> /usr/local/lib/perl5/site_perl/5.8.8/V6evalRemote.pm line 582 is:
> 
> $Remote = Expect->spawn("$TermCmd");
> ===================================
> Can you please let me know what is the problem here? I searched in Google
> and found one discussion forum: 
> http://kerneltrap.org/index
> php?q=mailarchive/freebsd-bugs/2008/11/17/4144314 , which reports similar
> issue.
> 
> if this is a problem with the latest version of the perl modules, how should
> I go back to the older version?
> 
> Thanks in advance,
> 
> Swaprava


-- 
Yukiyo Akisada <akisada@tahi.org>