Bug 4336
Summary: | screeen -wipe doesn't work for named screens | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Jay Freeman <saurik> |
Component: | screen | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 1.0 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-08-31 14:58:00 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
Jay Freeman
1999-08-03 21:40:50 UTC
Does this problem persist in the latest screen-3.9.4 from Raw Hide? Yes, the problem persists in screen-3.9.4. Sorry, have had a hard time checking e-mail lately, upgraded my motherboard and luck would have it my harddrive went bad too. From what I can tell, the problem is simply in how screen keeps track of information, in the filenames of the pipes. It performs the following check to see if it is a Remote socket or a Dead socket: if (matchlen || (*n == '.' && n[1] && strncmp(HostName, n + 1, strlen(n + 1)) == 0)) Named sockets don't include the terminal nor the hostname in the filename, therefor causing the local hostname check to fail. A possible solution to this is to modify screen to store the name of the screen after (or before, whatever) the existing terminal and hostname data as opposed to replacing it. That way it could perform that check just like it is, and continue to work without MAJOR design modifications. (This might be something for the screen people though since it isn't really a bug as much as a misplaced feature.) As this is more of a 'feature request' than a bug, we probably won't fix this here - contacting the screen developers would be your best bet. |