Bug 3901 – autoexpect says the system has no more PTYs

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 3901 - autoexpect says the system has no more PTYs

Summary:	autoexpect says the system has no more PTYs

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	exmh (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-07-05 12:15 EDT by Andreas Busch
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-08-28 18:16:17 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andreas Busch 1999-07-05 12:15:50 EDT

BTW: expect-5.28-29.i386.rpm is not listed in components.

expect-scripts and autoexpect script generation doesn't
work anymore with the new Unix 98 pty compiled into the
kernel (my version 2.2.10)
Increasing the number of pty's doesn't solve the problem.

[root@zuse1 /root]# autoexpect
autoexpect started, file is script.exp
The system has no more ptys.  Ask your system administrator
to create more.
    while executing
"spawn -noecho $env(SHELL)"
    (file "/usr/bin/autoexpect" line 317)

Comment 1 Jeff Johnson 1999-08-28 18:16:59 EDT

Make sure that /dev/pts is mounted. You should have a line in
/etc/fstab like
none                    /dev/pts        devpts  gid=5,mode=620  0 0

I don't know of any other problems like this. Please reopen this
bug if my analysis is wrong.

Note You need to log in before you can comment on or make changes to this bug.