Closed
Bug 1030088
Opened 10 years ago
Closed 10 years ago
Cannot reconnect to screen via a SSH session due to missing /dev/pts/0 permissions
Categories
(Infrastructure & Operations :: RelOps: Puppet, task)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: whimboo, Unassigned)
Details
Screen is not working as expected at least on the Ubuntu machines. When I connect via SSH and want to reconnect via 'screen -x' I get the following error: Cannot open your terminal '/dev/pts/0' - please check The reason for this is that the permissions are wrongly set. Looks like we only update pts/1 for the builder user: crw------- 1 root tty 136, 0 Jun 25 05:33 0 crw--w---- 1 mozauto tty 136, 1 Jun 25 04:44 1 crw--w---- 1 root tty 136, 2 Jun 23 06:24 2 crw--w---- 1 root tty 136, 5 Jun 23 06:26 5 c--------- 1 root root 5, 2 Jun 22 23:24 ptmx We may also want to update the permissions at least for pts/0 too.
Reporter | ||
Comment 1•10 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #0) > We may also want to update the permissions at least for pts/0 too. As turned out while reading different pages on the web this is not the proposed solution. Better is to call 'script /dev/null' here, or using another terminal multiplexer like http://blog.hawkhost.com/2010/06/28/tmux-the-terminal-multiplexer/
Reporter | ||
Comment 2•10 years ago
|
||
Actually this happens when you run 'su %builder%' when logged in as e.g. root, and then trying to invoke screen. So maybe we should not do anything here, and better login as the builder user directly. If su is used, the person has to manually call script. Dustin, shall we close as wontfix?
Comment 3•10 years ago
|
||
Sounds good to me. In general, I try to avoid changing user ids in a session -- if I need root access, I login as root, and if I need user-level access, I login as that user. Interference with screen sessions and the like is one reason for that preference :)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•