URL:
<https://savannah.gnu.org/bugs/?61534>
Summary: long session names break screen with no error
message/rails
Project: GNU Screen
Submitted by: None
Submitted on: Tue 23 Nov 2021 07:22:00 PM UTC
Category: Program Logic
Severity: 3 - Normal
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Release: 4.8.0
Discussion Lock: Any
Fixed Release: None
Planned Release: None
Work Required: None
_______________________________________________________
Details:
screen will allow you to specify a long session name without error, but does
not work if your session name is too long. For initial sessions, this causes
there to be no session created, but no error:
jmcminn@dukhat:~$ screen -S
averyverylongsesssionnameaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
-d -m bash -c 'ping -c 600 localhost'
jmcminn@dukhat:~$ screen -ls
No Sockets found in /run/screen/S-jmcminn.
jmcminn@dukhat:~$
For renamed sessions, the rename command takes, but results in a "Dead"
session that cannot be attached to or further interacted with:
jmcminn@dukhat:~$ screen -S shortname -d -m bash -c 'ping -c 600 localhost'
jmcminn@dukhat:~$ screen -ls
There is a screen on:
102297.shortname (11/23/2021 11:00:57 AM) (Detached)
1 Socket in /run/screen/S-jmcminn.
jmcminn@dukhat:~$ screen -S shortname -X sessionname
averyverylongsesssionnameaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
jmcminn@dukhat:~$ screen -ls
There is a screen on:
102297.averyverylongsesssionnameaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
(11/23/2021
11:00:58 AM) (Dead ???)
Remove dead screens with 'screen -wipe'.
1 Socket in /run/screen/S-jmcminn.
jmcminn@dukhat:~$
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61534>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
