Bug 676663

Summary:	screen can't be used when the home directory can't hold sockets
Product:	[Fedora] Fedora	Reporter:	Nalin Dahyabhai <nalin>
Component:	screen	Assignee:	Miroslav Lichvar <mlichvar>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	mlichvar, redhat-bugzilla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-10 17:27:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nalin Dahyabhai 2011-02-10 16:34:49 UTC

Description of problem:
Since bug #667252, screen's socket directory has been moved to the user's home directory.  My home directory's on a filesystem that doesn't support sockets (AFS), so it now fails to start.

Version-Release number of selected component (if applicable):
screen-4.1.0-0.1.20101110git066b098.fc15.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Log in with an AFS home directory.
2. Run "screen -DR".
  
Actual results:
bind (/afs/devel.redhat.com/users/nalin/.screen/7082.pts-2.blade): Operation not permitted

Expected results:
New screen.

Comment 1 Miroslav Lichvar 2011-02-10 17:27:03 UTC

Socket directory moved back to /var/run/screen in screen-4.1.0-0.3.20101110git066b098.fc15.

Comment 2 Nalin Dahyabhai 2011-02-10 17:56:10 UTC

Cool.  Thanks!