screen-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[screen-devel] [bug #43744] screen -d -r <string> connects to wrong scre


From: anonymous
Subject: [screen-devel] [bug #43744] screen -d -r <string> connects to wrong screen instance or gives an error
Date: Wed, 03 Dec 2014 10:06:19 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0

URL:
  <http://savannah.gnu.org/bugs/?43744>

                 Summary: screen -d -r <string> connects to wrong screen
instance or gives an error
                 Project: GNU Screen
            Submitted by: None
            Submitted on: Wed 03 Dec 2014 10:06:18 AM UTC
                Category: Program Logic
                Severity: 3 - Normal
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                 Release: None
           Fixed Release: None
         Planned Release: None
           Work Required: None

    _______________________________________________________

Details:

In the following lines, I'm indenting commands executed inside screen...

The setup:
$ screen -S RDV
  $ echo "here is DEV"
  here is DEV
[detached from 5266.RDV]
$ screen -S RDVdev
  $ echo "here is NOT DEV"
  here is NOT DEV
[detached from 5737.RDVdev]

Under Debian wheezy & screen 4.01.00devel
I get 
$ screen -d -r RDV
  here is DEV
[detached from 7847.RDVdev] ## <= wrong instance
$ screen -d -r RDVdev
  here is DEV
[detached from 7847.RDVdev]

Under Ubuntu 14.10 & screen 4.02.01
I get 
$ screen -d -r RDVdev
  here is DEV
[detached from 7847.RDVdev]
$ screen -d -r RDV
WriteMessage: Bad file descriptor ## <= error




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?43744>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]