Public bug reported:
Binary package hint: screen
Install ubuntu, then start screen with otions "-dm":
screen -dm top
looking into /var/run/screen/S-userwhostartedscreenwith-dmS you'll find
the directory empty (if it was before), or if there are files, no socket
referencing the running screen instance.
screen -dmS top top
does behave the same.
You may recreate the socket by issuing "kill -CHLD screeninstance-pid", but
that is at least annoying, or not useful if you started more than only a few
screen sessions.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: screen 4.0.3-14ubuntu1.2
ProcVersionSignature: Ubuntu 2.6.32-27.49-generic-pae 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-generic-pae i686
Architecture: i386
Date: Mon Dec 27 14:36:09 2010
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release i386
(20100427)
ProcEnviron:
LC_CTYPE=en_US.UTF-8
PATH=(custom, user)
SHELL=/bin/zsh
SourcePackage: screen
** Affects: screen (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/694732
Title:
screen does not create socket if started with options -dm
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
