Changes between Initial Version and Version 2 of Ticket #40872


Ignore:
Timestamp:
Oct 28, 2013, 4:12:54 PM (11 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #40872

    • Property Summary changed from attach in multiuser mode fails with "Attach attempt with bad pid" message to screen: attach in multiuser mode fails with "Attach attempt with bad pid" message
    • Property Port screen added

  • Ticket #40872 – Description

    initial v2  
    22by setting the screen executable to setuid root and executing the following
    33commands for a screen:
    4 ```
     4{{{
    55multiuser on
    66acladd OTHER_USER_ID
    7 ```
     7}}}
    88When screen is working properly, one user can start a screen with `screen -S SCREEN_NAME`
    99while OTHER_USER_ID joins the same screen with `screen -x FIRST_USER_ID/SCREEN_NAME`.
    … …  
    1515
    1616The source of the problem is a line that looks like this in socket.c:
     17{{{
    1718UserReturn(kill(pid, 0))
     19}}}
    1820
    1921Apparently, the kill runs in the context of the real user id instead of
    … …  
    3032
    3133i.e.:
     34{{{
    3235perl -p -i -e  's/UserReturn\(kill\(pid, 0\)\)/return 0/' socket.c
     36}}}
    3337
    3438I have tested the patch and it solves the problem although I am not sure