Bug 6008 – screen is completely unusable

Bug 6008 - screen is completely unusable

Summary:	screen is completely unusable

Status:	CLOSED WONTFIX

Aliases:	None

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

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-10-16 19:19 EDT by chauvin
Modified:	2014-03-16 22:10 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-11-01 13:52:08 EST
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 chauvin 1999-10-16 19:19:18 EDT

screen is _completely unusable_ under rh6.1.

for example, try the following:

% screen
CNTRL-a d

% screen -ls

no screens are seen even though the sockets appear to have
been created.  what's worse is that the screen session
itself goes into an inifinite loop at this point.

workaround:  the version shipped with rh 6.0 works well.

question:  the new version puts the screen sockets in the
home directory (which can be NFS mounted for many users).
why the change from the previous versions in which
/tmp/screens was used for this purpose?

Comment 1 Bill Nottingham 1999-10-17 00:06:59 EDT

Hmm... can't reproduce this here. The sequence you mention
correctly shows one detached screen socket.

Do you have /dev/pts mounted?

As for the moving the screen sockets into the home directory,
it's to avoid security issues with having them in /tmp.

Comment 2 Bill Nottingham 1999-10-18 09:26:59 EDT

According to the kernel folks, NFSv2 doesn't specify named
pipes, so the behavior is undefined. NFSv3 does. So that
would be the problem.

Comment 3 Bill Nottingham 1999-10-29 16:33:59 EDT

In this case, I think the only thing we can suggest is to
build screen to not use home directories for cases like this.

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