On Wed, Dec 29, 2021 at 00:01:38 -0500, Adam Russell wrote: > This is what I see > > -bash-5.1$ /usr/pkg/bin/screen -S some-session -p 0 -m -d > -bash-5.1$ screen -X quit > -bash-5.1$ /usr/pkg/bin/screen -S some-session -p 0 -m -d > -bash-5.1$ screen -X quit > No screen session found.
I was going to say I can't reproduce it, but then I could. I couldn't reproduce the problem as is, but I have screenrc that starts a bunch of windows, so I tested with -c /dev/null and then I do see the problem. The second invocation doesn't start the new screen, just as you show. But if you wait a little bit (about 5 seconds it would seem) after the first session is quat, then the new session is created ok again. [pardon my bash^Wcsh'isms, but i think it's appropriate here as it indicates the command is repeated as-is from history and spares the reader doing the verfication] $ screen -S test -c /dev/null -d -m -p 0; screen -ls; screen -S test -X quit There is a screen on: 6098.pts-0.nbvio (Detached) 1 Socket in /tmp/screens/S-uwe. No screen session found. $ !! screen -S test -c /dev/null -d -m -p 0; screen -ls; screen -S test -X quit There are screens on: 6098.pts-0.nbvio (Detached) 2902.test (Detached) 2 Sockets in /tmp/screens/S-uwe. $ !! screen -S test -c /dev/null -d -m -p 0; screen -ls; screen -S test -X quit There is a screen on: 6098.pts-0.nbvio (Detached) 1 Socket in /tmp/screens/S-uwe. No screen session found. $ !! screen -S test -c /dev/null -d -m -p 0; screen -ls; screen -S test -X quit There are screens on: 6098.pts-0.nbvio (Detached) 14114.test (Detached) 2 Sockets in /tmp/screens/S-uwe. This is with natural typing pace. -uwe