Changes between Initial Version and Version 2 of Ticket #40872
- Timestamp:
- Oct 28, 2013, 4:12:54 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #40872
-
Property
Summary
changed from
attach in multiuser mode fails with "Attach attempt with bad pid" message
toscreen: attach in multiuser mode fails with "Attach attempt with bad pid" message
- Property Port screen added
-
Property
Summary
changed from
-
Ticket #40872 – Description
initial v2 2 2 by setting the screen executable to setuid root and executing the following 3 3 commands for a screen: 4 ``` 4 {{{ 5 5 multiuser on 6 6 acladd OTHER_USER_ID 7 ``` 7 }}} 8 8 When screen is working properly, one user can start a screen with `screen -S SCREEN_NAME` 9 9 while OTHER_USER_ID joins the same screen with `screen -x FIRST_USER_ID/SCREEN_NAME`. … … 15 15 16 16 The source of the problem is a line that looks like this in socket.c: 17 {{{ 17 18 UserReturn(kill(pid, 0)) 19 }}} 18 20 19 21 Apparently, the kill runs in the context of the real user id instead of … … 30 32 31 33 i.e.: 34 {{{ 32 35 perl -p -i -e 's/UserReturn\(kill\(pid, 0\)\)/return 0/' socket.c 36 }}} 33 37 34 38 I have tested the patch and it solves the problem although I am not sure