[Expectperl-discuss] pty allocation problem on RedHat Enterprise Linux 4

[Sowmya K. <skr...@bd...>]

Hi,
We are testing our product on RedHat Enterprise Linux 4 Update 4 and are
experiencing problems with pty allocation. In our code we use Expect.pm.
What happens is that after a few Expect sessions are created and
destroyed, pty allocation fails. Once this occurs, I am not able to
allocate Ptys for any other program - for e.g after this problem occurs,
when I try to SSH to the machine, it would fail with "Server refused to
allocate Pty".=20
I am using IO-Tty-1.07 and Expect-1.20.=20
After a few Expect sessions, this is the error I see:

pty_allocate(nonfatal): getpt(): No such file or directory at
.../IO/Pty.pm line 24.
 pty_allocate(nonfatal): openpty(): No such file or directory at
.../IO/Pty.pm line 24.
 pty_allocate(nonfatal): open(/dev/ptmx): Input/output error at
.../IO/Pty.pm line 24.
 Cannot open a pty at ...

Actually, someone else has also seen exactly the same problem on RedHat
Enterprise Linux 4.=20
http://sourceforge.net/mailarchive/forum.php?thread_id=3D7450783&forum_id=
=3D
6382
But I don't see any responses to his posting.

P.S We have not seen this problem on RedHat Enterprise Linux 3 with
IO-Tty-1.02 and Expect-1.15. With these versions of IO::Tty and
Expect.pm, I saw the same issue as stated above on RedHat Enterprise
Linux 4, hence thought if I update to the most recent (IO-Tty-1.07 and
Expect-1.20), the problem would go away, but unfortunately, I still see
the same issue.

I would greatly appreciate your help in this regard.

Thanks in advance
-Sowmya=20
=20
--------------------------------------------------------

This email and any files transmitted with it are confidential and are =
intended solely for the use of the individual or entity to whom they are =
addressed. This communication may contain material protected by the =
attorney-client privilege. If you are not the intended recipient, be =
advised that any use, dissemination, forwarding, printing or copying is =
strictly prohibited. If you have received this email in error, please =
contact the sender and delete all copies.