Penguin
Recent Changes

Differences between version 9 and predecessor to the previous major change of Screen.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 9 Last edited on Monday, May 8, 2006 9:45:35 am by MichaWie Revert
Older page: version 8 Last edited on Monday, April 10, 2006 1:43:50 pm by CraigBox Revert
@@ -11,5 +11,5 @@
 * You should really read the screen(1) ManPage -- the program is chock full of useful bits. 
 * <tt>screen -rx</tt> allows to to attach to an existing screen session, even if you are already attached to it from another terminal. 
 * If you use Ctrl-A a lot and don't like screen catching this, you can change the key used for this by adding <tt>escape ^ss</tt> or similar to <tt>~~/.screenrc</tt>. The first character, <tt>^s</tt> defines the escape char, the second character is what you press after an escape to send a literal escape sequence. 
 * The documentation is not quite clear on how to launch processes into new windows in a running [Screen] session. The <tt>-m -d</tt> switch combination advertised for launching processes in detached mode creates an entire session for each of them. If you want them running in an existing session, you have to send that session the <tt>screen</tt> command. Sending commands to a session from the [Shell] is done by invoking <tt>screen -X ''command''</tt>. Effectively, this means that you launch a batch of wget(1) downloads in a screen session by invoking <tt>screen -X screen wget ''$someurl''</tt> in a loop. 
-* If you su to a user and then get a message like ''Cannot open your terminal '/dev/pts/7' - please check'', you need to change the permissions on your terminal __before__ the su, so you can write to it from the new user: <tt>chmod 777 `tty`</tt>. 
+* If you su to a user and then get a message like ''Cannot open your terminal '/dev/pts/7' - please check'', you need to change the permissions on your terminal __before__ the su, so you can write to it from the new user: <tt>chmod 777 `tty`</tt>. Although the chmod works it is not the right solution to the problem. The problem itself is explained here: http://searchopensource.techtarget.com/tip/,289483,sid39_gci1102088,00.html In short: if you (user1) su to user2 your terminal device /dev/pts/* still belongs to user1. This wont happen if user2 directly logs in or if you use ssh to login. Try user2@localhost, that should work .