From MAILER-DAEMON Wed Feb 02 00:24:16 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1CwCzu-0002TV-NE for mharc-screen-users@gnu.org; Wed, 02 Feb 2005 00:24:14 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CwCzY-0002My-10 for screen-users@gnu.org; Wed, 02 Feb 2005 00:23:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CwCzQ-0002Ix-7k for screen-users@gnu.org; Wed, 02 Feb 2005 00:23:45 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CwCzP-0002H5-Fg for screen-users@gnu.org; Wed, 02 Feb 2005 00:23:43 -0500 Received: from [4.12.9.117] (helo=chancroid.omgwallhack.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CwCdO-0001BA-MC for screen-users@gnu.org; Wed, 02 Feb 2005 00:00:59 -0500 Received: from [66.241.75.4] (helo=amebiasis.omgwallhack.org) by chancroid.omgwallhack.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id 1CwCdJ-0001t4-9J for screen-users@gnu.org; Tue, 01 Feb 2005 21:00:53 -0800 Date: Tue, 1 Feb 2005 21:00:37 -0800 From: Julian Blake Kongslie To: screen-users@gnu.org Message-ID: <20050201210037.67e60e9d@amebiasis.omgwallhack.org> X-Mailer: Sylpheed-Claws 1.0.0 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Title escape sequence X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 05:24:04 -0000 When a program running within a screen session issues the k sequence, it can change the title of the current screen window. Is there any way to disable this feature? I have to deal with a closed-source program that constantly changes my window titles to nonsense. Disabling termcap reporting of this feature isn't really a solution for me, because the program is hard-coded to output the sequence and doesn't check termcap. Thanks, -- -Julian Blake Kongslie From MAILER-DAEMON Thu Feb 03 13:32:20 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1CwliK-0006ie-9P for mharc-screen-users@gnu.org; Thu, 03 Feb 2005 13:28:24 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Cwli7-0006dv-L8 for screen-users@gnu.org; Thu, 03 Feb 2005 13:28:12 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Cwlhu-0006Xc-O8 for screen-users@gnu.org; Thu, 03 Feb 2005 13:28:00 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cwlhu-0006XS-MS for screen-users@gnu.org; Thu, 03 Feb 2005 13:27:58 -0500 Received: from [213.46.255.25] (helo=viefep12-int.chello.at) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CwlU2-00076k-0M for screen-users@gnu.org; Thu, 03 Feb 2005 13:13:38 -0500 Received: from Dingo ([213.47.104.218]) by viefep12-int.chello.at (InterMail vM.6.01.03.05 201-2131-111-107-20040910) with ESMTP id <20050203181336.IGLY24925.viefep12-int.chello.at@Dingo> for ; Thu, 3 Feb 2005 19:13:36 +0100 From: Christian Taylor To: screen-users@gnu.org Date: Thu, 3 Feb 2005 17:43:29 +0100 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502031743.29523.cht@chello.at> Subject: Description of window flags (specifically "$") X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2005 18:28:17 -0000 Hello screen-users, I'm using "caption always" with the string escapes %(+ or -)Lw and %f to display the window flags. However, on some systems every window has a "$" flag, while on other systems (running the same screen version of 4.00.02), no window has this flag. I have no idea what this means, since I can't find a description of the window flags anywhere in the screen manual. Googling doesn't help either. Does anyone know where to find this information? Thanks, Christian Taylor From MAILER-DAEMON Thu Feb 03 20:59:10 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1CwskS-0005fl-Q8 for mharc-screen-users@gnu.org; Thu, 03 Feb 2005 20:59:04 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CwskM-0005ZN-P3 for screen-users@gnu.org; Thu, 03 Feb 2005 20:58:59 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CwskD-0005U6-Jj for screen-users@gnu.org; Thu, 03 Feb 2005 20:58:53 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CwskC-0005QW-Jy for screen-users@gnu.org; Thu, 03 Feb 2005 20:58:48 -0500 Received: from [204.127.202.55] (helo=sccrmhc11.comcast.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CwsPd-0002TY-Ph for screen-users@gnu.org; Thu, 03 Feb 2005 20:37:33 -0500 Received: from durin.aperiodic.net (pcp01840557pcs.owngsm01.md.comcast.net[68.32.120.226]) by comcast.net (sccrmhc11) with ESMTP id <2005020401373201100ceufpe>; Fri, 4 Feb 2005 01:37:32 +0000 Received: from mithrandir.aperiodic.net (mithrandir.aperiodic.net [192.168.1.192]) by durin.aperiodic.net (Postfix) with ESMTP id C1340384006 for ; Thu, 3 Feb 2005 20:37:30 -0500 (EST) Received: by mithrandir.aperiodic.net (Postfix, from userid 1000) id 96A6C3B76CC6; Thu, 3 Feb 2005 20:37:30 -0500 (EST) Date: Thu, 3 Feb 2005 20:37:30 -0500 From: Phil!Gregory To: screen-users@gnu.org Message-ID: <20050204013730.GT31825@mithrandir.aperiodic.net> Mail-Followup-To: screen-users@gnu.org References: <200502031743.29523.cht@chello.at> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200502031743.29523.cht@chello.at> User-Agent: Mutt/1.5.6+20040907i Subject: Re: Description of window flags (specifically "$") X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2005 01:59:02 -0000 * Christian Taylor [2005-02-03 17:43 +0100]: > I can't find a description of the window flags anywhere in the screen > manual. Googling doesn't help either. Yeah, generic names like "screen" make Google searches a bit difficult. :) The window flags appear to be documented in the man page under the 'windows' command: Each window is listed by number with the name of process that has been started in the window (or its title); the current window is marked with a ‘*’; the previous window is marked with a ‘-’; all the windows that are "logged in" are marked with a ‘$’; a background window that has received a bell is marked with a ‘!’; a background window that is being monitored and has had activity occur is marked with an ‘@’; a window which has output logging turned on is marked with ‘(L)’; windows occupied by other users are marked with ‘&’; windows in the zombie state are marked with ‘Z’. -- ...computer contrarian of the first order... / http://aperiodic.net/phil/ PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 --- -- #define NULL 0 /* silly thing is, we don't even use this */ -- perl.c, perl source code ---- --- -- From MAILER-DAEMON Fri Feb 04 15:33:29 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1CxA8v-0007hz-Od for mharc-screen-users@gnu.org; Fri, 04 Feb 2005 15:33:29 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CxA8t-0007gU-Jm for screen-users@gnu.org; Fri, 04 Feb 2005 15:33:27 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CxA8r-0007fs-KC for screen-users@gnu.org; Fri, 04 Feb 2005 15:33:26 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CxA6B-0006kt-GJ for screen-users@gnu.org; Fri, 04 Feb 2005 15:30:39 -0500 Received: from [213.46.255.21] (helo=viefep18-int.chello.at) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Cx9Z8-0001q9-0t for screen-users@gnu.org; Fri, 04 Feb 2005 14:56:30 -0500 Received: from Dingo ([213.47.104.218]) by viefep18-int.chello.at (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20050204195628.MXJK23481.viefep18-int.chello.at@Dingo> for ; Fri, 4 Feb 2005 20:56:28 +0100 From: Christian Taylor To: screen-users@gnu.org Date: Fri, 4 Feb 2005 20:56:00 +0100 User-Agent: KMail/1.7.2 References: <200502031743.29523.cht@chello.at> <20050204013730.GT31825@mithrandir.aperiodic.net> In-Reply-To: <20050204013730.GT31825@mithrandir.aperiodic.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502042056.00834.cht@chello.at> Subject: Re: Description of window flags (specifically "$") X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2005 20:33:28 -0000 On Friday 04 February 2005 02:37, Phil!Gregory wrote: > * Christian Taylor [2005-02-03 17:43 +0100]: > > I can't find a description of the window flags anywhere in the screen > > manual. Googling doesn't help either. > > The window flags appear to be documented in the man page under the > 'windows' command: > [...] Guess I should have been more thorough, I never thought of looking there. Thanks for your help! Christian From MAILER-DAEMON Sat Feb 05 19:23:33 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1CxaD6-00056p-AN for mharc-screen-users@gnu.org; Sat, 05 Feb 2005 19:23:33 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CxaCt-00052v-Ka for screen-users@gnu.org; Sat, 05 Feb 2005 19:23:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CxaCh-0004wp-BE for screen-users@gnu.org; Sat, 05 Feb 2005 19:23:11 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CxaCg-0004t2-KS for screen-users@gnu.org; Sat, 05 Feb 2005 19:23:06 -0500 Received: from [216.18.70.245] (helo=mail.lynx.bc.ca) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CxZlD-0000KA-SQ for screen-users@gnu.org; Sat, 05 Feb 2005 18:54:44 -0500 Received: from yahoo.ca (vanip-128-010.eseenet.com [66.38.128.10]) by mail.lynx.bc.ca (8.13.1/8.13.1) with ESMTP id j15Nsffm027730 for ; Sat, 5 Feb 2005 15:54:42 -0800 (PST) X-Authentication-Warning: mail.lynx.bc.ca: Host vanip-128-010.eseenet.com [66.38.128.10] claimed to be yahoo.ca Message-ID: <42055F05.5080406@yahoo.ca> Date: Sat, 05 Feb 2005 16:04:21 -0800 From: Simon Pole User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030915 X-Accept-Language: en-us, en MIME-Version: 1.0 To: screen-users@gnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Subject: re: tabbed browsing with screen X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Feb 2005 00:23:25 -0000 Hi Screen-Users, Using lynx, I've set up screen to enable tabbed browsing as seen in the Mozilla-Firefox browsers. The way I did it seems a bit clunky, and I wondered if anyone else could see a more elegant way of doing it. 1) Opening html links from lynx in another window. I added a call to a shellscript from lynx.cfg like this: EXTERNAL:http:screen_url.sh %s:TRUE (where %s is the link to be passed to the shellscript) The screen_url.sh is one line: screen -X exec screen -t "$*" lynx "$*" (Lynx must be compiled with the use externals flag. The "." character is then used to open the highlighted link in a new window.) 2) Text links To enable tabbed browsing of non-html links, I first created the source file "turltrig.scr" with these commands: writebuf exec texturl.sh The texturl.sh script was this: U=$(cat /tmp/screen-exchange) screen -t $U lynx $U Then a new binding in screenrc to execute the source file: bind ^t source turltrig.scr The following process then opens text links in a new window: 1) Enter copy mode and highlight link to be opened. 2) ^t to call the source file and write the highlighed link to /tmp/screen-exchange 3) The texurl.sh script then passes the link from the screen-exchange file to lynx in a new window. Can anyone see a better way of doing this? Cheers Simon Pole From MAILER-DAEMON Sat Feb 05 21:58:36 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Cxcd9-0000Oz-Ij for mharc-screen-users@gnu.org; Sat, 05 Feb 2005 21:58:35 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Cxcd0-0000Lw-8h for screen-users@gnu.org; Sat, 05 Feb 2005 21:58:27 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Cxccu-0000JK-KH for screen-users@gnu.org; Sat, 05 Feb 2005 21:58:21 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cxccu-0000FX-1B for screen-users@gnu.org; Sat, 05 Feb 2005 21:58:20 -0500 Received: from [128.227.74.42] (helo=smtp.ufl.edu) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1Cxc6P-00068n-UX for screen-users@gnu.org; Sat, 05 Feb 2005 21:24:46 -0500 Received: from osgjas03.cns.ufl.edu (osgjas03.cns.ufl.edu [128.227.74.133]) by smtp.ufl.edu (8.13.1/8.13.1/2.5.0) with ESMTP id j162Ohw4052474; Sat, 5 Feb 2005 21:24:43 -0500 Message-ID: <1020288155.1107656683293.JavaMail.osg@osgjas03.cns.ufl.edu> Date: Sat, 5 Feb 2005 21:24:43 -0500 (EST) From: Raymond Page To: Simon Pole , screen-users@gnu.org Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: GatorMail WebMail (http://open-systems.ufl.edu/software/) X-Originating-IP: 68.214.99.29 [68.214.99.29] X-UFL-Spam-Status: hits=-1.428, required=5, tests=BAYES_20 X-Scanned-By: CNS Open Systems Group (http://open-systems.ufl.edu/services/smtp-relay/) X-UFL-Scanned-By: CNS Open Systems Group (http://open-systems.ufl.edu/services/smtp-relay/) Cc: Subject: re: tabbed browsing with screen X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Feb 2005 02:58:29 -0000 Please don't think of screen as a way to make your favorite application tabbable. Your application should inherently support something like that. For text mode webbrowsing, elinks already provides tabbed browsing. -- Raymond Page On Sat Feb 05 19:04:21 EST 2005, Simon Pole wrote: > Hi Screen-Users, > > Using lynx, I've set up screen to enable tabbed browsing as seen > in the Mozilla-Firefox browsers. The way I did it seems a bit > clunky, and I wondered if anyone else could see a more elegant > way of doing it. > > 1) Opening html links from lynx in another window. > > I added a call to a shellscript from lynx.cfg like this: > > EXTERNAL:http:screen_url.sh %s:TRUE > > (where %s is the link to be passed to the shellscript) > > The screen_url.sh is one line: > > screen -X exec screen -t "$*" lynx "$*" > > (Lynx must be compiled with the use externals flag. The "." > character is then used to open the highlighted link in a new > window.) > > 2) Text links > > To enable tabbed browsing of non-html links, I first created the > source file "turltrig.scr" with these commands: > > writebuf > exec texturl.sh > > The texturl.sh script was this: > > U=$(cat /tmp/screen-exchange) > screen -t $U lynx $U > > Then a new binding in screenrc to execute the source file: > > bind ^t source turltrig.scr > > The following process then opens text links in a new window: > > 1) Enter copy mode and highlight link to be opened. > 2) ^t to call the source file and write the highlighed link to > /tmp/screen-exchange > 3) The texurl.sh script then passes the link from the > screen-exchange file to lynx in a new window. > > Can anyone see a better way of doing this? > > Cheers > Simon Pole > > > > _______________________________________________ > screen-users mailing list > screen-users@gnu.org > http://lists.gnu.org/mailman/listinfo/screen-users > > From MAILER-DAEMON Mon Feb 07 16:57:51 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1CyGpn-0007dV-SN for mharc-screen-users@gnu.org; Mon, 07 Feb 2005 16:54:19 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CyGpY-0007Xy-Mg for screen-users@gnu.org; Mon, 07 Feb 2005 16:54:04 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CyGpK-0007Qu-IA for screen-users@gnu.org; Mon, 07 Feb 2005 16:53:54 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CyGpJ-0007OD-SH for screen-users@gnu.org; Mon, 07 Feb 2005 16:53:49 -0500 Received: from [192.109.42.66] (helo=antilope.in-berlin.de) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CyGXX-0005BB-Uv for screen-users@gnu.org; Mon, 07 Feb 2005 16:35:28 -0500 Received: from antilope.in-berlin.de (localhost [127.0.0.1]) by antilope.in-berlin.de (8.12.11/8.12.11/Debian-4) with ESMTP id j17LZ2H8011721 for ; Mon, 7 Feb 2005 22:35:02 +0100 Received: (from plenz@localhost) by antilope.in-berlin.de (8.12.11/8.12.11/Debian-4) id j17LYwNS011660 for screen-users@gnu.org; Mon, 7 Feb 2005 22:34:58 +0100 X-Authentication-Warning: antilope.in-berlin.de: plenz set sender to jp@cvmx.de using -f Date: Mon, 7 Feb 2005 22:34:57 +0100 From: Julius Plenz To: screen-users@gnu.org Message-ID: <20050207213457.GJ26700@cvmx.de> Mail-Followup-To: screen-users@gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-PGP-Key: 0x186DCA0D X-PGP-Fingerprint: 3993 FD19 2AF0 E21E 5D74 E963 144C 5EE9 186D CA0D X-URL: http://www.plenz.com/ X-Operating-System: Debian GNU/Linux 3.1 (Kernel 2.4.29) X-Editor: Vim 6.3 - set ai et ts=4 tw=70 comments=b:#, :%, fb:-, n:>, n:) nosm nonu User-Agent: Mutt/1.5.6i Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by antilope.in-berlin.de id j17LZ2H8011721 Subject: Oddities: =?iso-8859-1?q?=B0a_-=3E_=E4=2C_=B0u_-=3E_=B0u?= X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Feb 2005 21:54:10 -0000 hi! Yesterday, a really strange problem occured when modifying my screenrc. I added these lines (for typing german umlauts easier): bindkey -t =B0a stuff "=E4" bindkey -t =B0A stuff "=C4" bindkey -t =B0o stuff "=F6" bindkey -t =B0O stuff "=D6" bindkey -t =B0u stuff "=FC" bindkey -t =B0U stuff "=DC" bindkey -t =B0s stuff "=DF" (by the way, this is copied from http://michael-prokop.at/computer/config/.screenrc ) having the screenrc re-sourced, something really weird happens: =B0a, =B0A, =B0U, =B0O produce correct Umlauts, but =B0s, =B0u and =B0o refuse = to do their work. Hitting =B0 and s just produces =B0s, whereas hitting =B0a produces a "=E4". Anyone got an idea why screen behaves like this? Julius --=20 c=3D"JAzJ.t uqws4th zGaFn bmoit! hOeir, Rx3uzAbp yreWh hvYk, atTcRk5er, z= c".split( //);c.each_index{|i|1191339643030408809184.to_s(2)[i].chr.to_i>0&&$><; Fri, 11 Feb 2005 21:51:28 +0100 Received: from rs by mwilson.umlcoop.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Feb 2005 21:51:28 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: screen-users@gnu.org From: Rusty Shackleford Date: Fri, 11 Feb 2005 16:03:31 +0000 (UTC) Organization: Debian GNU/Linux site Lines: 10 Message-ID: X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mwilson.umlcoop.net User-Agent: slrn/0.9.8.0 (Linux) Sender: news X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner: Found to be clean X-MailScanner-From: gcgsu-screen-users@m.gmane.org X-MailScanner-To: screen-users@gnu.org Subject: How to include PWD into hardstatus line? X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Feb 2005 21:28:50 -0000 I tried adding $PWD to my hardstatus, but that seemed to store the initial directory and not update as I moved around. I couldn't find a % symbol for the current directory. Also, sometimes I start a screen on host XXX, then rsh to another host YYY, but the screen hardstatus still displays hostname XXX and cpu load average info for XXX. Is it possible to update that to YYY's hostname and load average? TIA From MAILER-DAEMON Sat Feb 12 18:56:50 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D0785-0007zI-ML for mharc-screen-users@gnu.org; Sat, 12 Feb 2005 18:56:49 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D0780-0007vt-TE for screen-users@gnu.org; Sat, 12 Feb 2005 18:56:45 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D074S-0006Kk-Up for screen-users@gnu.org; Sat, 12 Feb 2005 18:53:07 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D074Q-0006Dd-KZ for screen-users@gnu.org; Sat, 12 Feb 2005 18:53:02 -0500 Received: from [204.127.202.64] (helo=sccrmhc13.comcast.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D06et-0006Hw-As for screen-users@gnu.org; Sat, 12 Feb 2005 18:26:39 -0500 Received: from durin.aperiodic.net (pcp01840557pcs.owngsm01.md.comcast.net[68.32.120.226]) by comcast.net (sccrmhc13) with ESMTP id <2005021223263701600ies6he>; Sat, 12 Feb 2005 23:26:37 +0000 Received: from mithrandir.aperiodic.net (mithrandir.aperiodic.net [192.168.1.192]) by durin.aperiodic.net (Postfix) with ESMTP id 4A0F0384006 for ; Sat, 12 Feb 2005 17:52:56 -0500 (EST) Received: by mithrandir.aperiodic.net (Postfix, from userid 1000) id D445D3B76CC6; Sat, 12 Feb 2005 17:52:55 -0500 (EST) Date: Sat, 12 Feb 2005 17:52:55 -0500 From: Phil!Gregory To: screen-users@gnu.org Message-ID: <20050212225254.GB1308@mithrandir.aperiodic.net> Mail-Followup-To: screen-users@gnu.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: User-Agent: Mutt/1.5.6+20040907i Subject: Re: How to include PWD into hardstatus line? X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Feb 2005 23:56:46 -0000 * Rusty Shackleford [2005-02-11 16:03 +0000]: > I tried adding $PWD to my hardstatus, but that seemed to store the > initial directory and not update as I moved around. I couldn't find a % > symbol for the current directory. There's not really a good way to do what you want, though I'll provide something of a hack in a bit. The problem with $PWD is that it's an enivronment variable. screen will inherit $PWD from the process that ran it (presumably your shell), but it will not change $PWD, so you will always get the same value from it. The problem with some % escape is that you're probably not changing screen's working directory. If you start screen, screen starts a shell by default. When you change directories by 'cd', the shell is changing its working directory, but the screen process's working directory remains the same. (You can change screen's working directory via the 'chdir' sceen command, but I assume that's not what you're using.) You can hack this into screen by using the new backtick escapes. Put something like this in your .screenrc: backtick 1 15 15 cat %{HOME}/.pwd hardstatus "%H:%1`" Then modify your shell to write to ~/.pwd every time you change directories. The best approach would be if you use a shell that can run user-defined stuff right after changing directories (like zsh's chpwd), but I'll assume you're running bash, which only has $PROMPT_COMMAND. In your .bashrc (or .profile; I can never keep the two straight) put something like: PROMPT_COMMAND=3D'echo $PWD > ~/.pwd' Those will combine to put ":" in your hardstatus. The caveat is that it only really works if you only have one window in your screen session. If you've got multiple windows (or even multiple shells =66rom, say, several xterms), they'll keep overwriting each other's pwds. (Though you could change the PROMPT_COMMAND to '[ "$TERM" =3D "screen" ] && echo $PWD > ~/.pwd' to filter out all shells not running in screen.) > Also, sometimes I start a screen on host XXX, then rsh to another host > YYY, but the screen hardstatus still displays hostname XXX and cpu load > average info for XXX. Yes. Screen displays the name, load, and other characteristics of the computer it's running on. Even if you rsh to a different host, that screen session is still running on the original host; it just has an rsh session in it. > Is it possible to update that to YYY's hostname and load average? Probably, with some careful work and judicious use of backtick commands. Actual implementation is left as an exercise for the reader. }:> --=20 =2E..computer contrarian of the first order... / http://aperiodic.net/phil/ PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 --- -- You are standing in an open field west of a white house, with a boarded front door. There is a small mailbox here. ---- --- -- From MAILER-DAEMON Sat Feb 12 21:54:53 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D09uN-0004jb-6w for mharc-screen-users@gnu.org; Sat, 12 Feb 2005 21:54:51 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D09uF-0004ho-N6 for screen-users@gnu.org; Sat, 12 Feb 2005 21:54:44 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D09u5-0004cX-2w for screen-users@gnu.org; Sat, 12 Feb 2005 21:54:37 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D09u0-0004Yw-Sf for screen-users@gnu.org; Sat, 12 Feb 2005 21:54:29 -0500 Received: from [129.240.130.16] (helo=pat.uio.no) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D09Mm-0006mS-4k for screen-users@gnu.org; Sat, 12 Feb 2005 21:20:08 -0500 Received: from mail-mx2.uio.no ([129.240.10.30] ident=[U2FsdGVkX1/UfAuOxatYcuQdoun1by+nwGdIryUc2Hg=]) by pat.uio.no with esmtp (Exim 4.43) id 1D09Mj-00072E-A0 for screen-users@gnu.org; Sun, 13 Feb 2005 03:20:05 +0100 Received: from fire.ifi.uio.no ([129.240.65.212]) by mail-mx2.uio.no with esmtp (Exim 4.43) id 1D09Mh-0005pi-21 for screen-users@gnu.org; Sun, 13 Feb 2005 03:20:03 +0100 Received: from localhost (peder@localhost) by fire.ifi.uio.no ; Sun, 13 Feb 2005 03:20:02 +0100 (MET) Date: Sun, 13 Feb 2005 03:20:02 +0100 (MET) From: Peder Stray X-X-Sender: peder@fire.ifi.uio.no To: screen-users@gnu.org In-Reply-To: <20050212225254.GB1308@mithrandir.aperiodic.net> Message-ID: References: <20050212225254.GB1308@mithrandir.aperiodic.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning X-UiO-MailScanner: No virus found X-UiO-Spam-info: not spam, SpamAssassin (score=-5, required 12, autolearn=disabled, UIO_MAIL_IS_INTERNAL -5.00) Subject: Re: How to include PWD into hardstatus line? X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 02:54:46 -0000 On Sat, 12 Feb 2005, Phil!Gregory wrote: > * Rusty Shackleford [2005-02-11 16:03 +0000]: >> I tried adding $PWD to my hardstatus, but that seemed to store the >> initial directory and not update as I moved around. I couldn't find a % >> symbol for the current directory. > > There's not really a good way to do what you want, though I'll provide > something of a hack in a bit. i use %h in the hardstatus (the hardstatus of the shell/term) and use the "ESC]0;^G" escape in my prompt to set pwd and such in the hardstatus. No problems with the overwrite problems Phil mentioned, but programs running in screen could of cource use this escape themselves... -- Peder Stray From MAILER-DAEMON Sat Feb 12 23:00:12 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D0Avb-0006px-K2 for mharc-screen-users@gnu.org; Sat, 12 Feb 2005 23:00:11 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D0AqR-0006FW-Ss for screen-users@gnu.org; Sat, 12 Feb 2005 22:54:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D0Aq6-00066F-FA for screen-users@gnu.org; Sat, 12 Feb 2005 22:54:31 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D0Aq4-00062A-Dr for screen-users@gnu.org; Sat, 12 Feb 2005 22:54:28 -0500 Received: from [64.62.145.229] (helo=mx1.parodius.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D0ASO-0001DZ-PA for screen-users@gnu.org; Sat, 12 Feb 2005 22:30:01 -0500 Received: from pentarou.parodius.com (localhost [127.0.0.1]) by mx1.parodius.com (8.13.1/8.13.1) with ESMTP id j1D3TwwX090632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 12 Feb 2005 19:29:58 -0800 (PST) (envelope-from jdc@pentarou.parodius.com) Received: (from jdc@localhost) by pentarou.parodius.com (8.13.1/8.13.1/Submit) id j1D3Tw1t090631 for screen-users@gnu.org; Sat, 12 Feb 2005 19:29:58 -0800 (PST) (envelope-from jdc) Date: Sat, 12 Feb 2005 19:29:58 -0800 From: Jeremy Chadwick To: screen-users@gnu.org Message-ID: <20050213032958.GA89618@parodius.com> Mail-Followup-To: screen-users@gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.7i Subject: screen and ssh agents + agent forwarding X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 04:00:10 -0000 I apologise if this topic has been discussed before, but I have skimmed the archives and have not found anything relating to it. This issue has, on the other hand, been discussed a couple times on the old Yahoo Groups list, to no avail. Finding information about this problem is also a real pain, since search engine queries for the word "screen" will... well... I'm sure you know. This mail will hopefully place information into a standard location where future visitors can get information about the problem. Anyone here who has tried to use GNU screen alongside an ssh agent will know how painful it is to get things to work properly, especially when using the forwarding mechanism of ssh agents. It's a complete mess. If this is a new issue to you, let me explain the problem, and how GNU screen modifications can help alleviate this pain. If you don't want to read my explanation, and want something more concise, read this: http://www-106.ibm.com/developerworks/linux/library/l-keyc3/ SSH agents are essentially "key caches", induced/supported by the SSH client (such as SecureCRT or PuTTY, or in the case of *IX OpenSSH, ssh-agent(1)). When using an agent, environment variables are set up once the agent is configured. sshd actually maintains a socket file in /tmp (usually named /tmp/ssh-/agent.) when an SSH agent is used. This socket is removed when the user logs out (i.e. sshd detects a disconnect). Important to note: the and I speak of are specific to each SSH connection made to sshd; they are unique identifiers for that SSH session. When GNU screen is run, the SSH_AUTH_SOCK environment variable is imported from the parent shell which started screen, and is kept that way throughout all future spawned shells within screen. The problem is that if a user detaches from screen, logs out of the system, and logs back in, the agent socket created by sshd will no longer exist; therefore, the SSH_AUTH_SOCK variables within the shells spawned by screen now point to a non-existent directory and a non-existent socket file. Simply put, this breaks SSH agent forwarding. If my description here does not make sense, please read the following sites which contain information about the problem: http://www.deadman.org/sshscreen.html http://www.gentoo.org/proj/en/keychain/index.xml http://frogcircus.org/screen/ssh-agent The above two links contain workarounds for this problem, none of which truly address the problem -- and in some cases, actually induce MORE problems due to their methodology. The most common idea is to overwrite SSH_AUTH_SOCK, pointing to a static location (such as $HOME/.screen_ssh_sock), which is an actual symbolic link to the socket file (/tmp/ssh-). The framework to update the symbolic link is done in either .bash_profile (for bash users) or .login (for csh/tcsh users). This method has two major flaws: a. Requires the shell to have the ability to detect interactive vs. non-interactive login shells. Not all versions of bash support this methodology, resulting in something like scp(1) from another host to the host which has the dot-files breaking pre-existing symlinks. b. Assumes you will only have one ssh session to the machine the dot-files are running on. I.e. if you're logged into box "foo" from home (which has GNU screen attached), leave your machine connected, go to work, and ssh into "foo" from work, you will completely botch the symlink -- one you go home, you will find that the symlink points to the agent socket file created when you logged in from work. You now have to manually remove the symlink and point it to the right place for agent forwarding to again work. c. A workaround for this method could be to "detect" if you're already connected to the machine elsewhere and therefore not update the symlink, but this is quite horrible to do: anyone who argues with me on this is flat-out wrong. Period. I have used this method (rather than using other peoples' example dot-file scripts, I wrote it myself), and ran into Issue B quite often. Issue A I encounter at my workplace, with no solution (I do not maintain the systems, and I have asked for a bash upgrade -- at least to 2.05b -- almost 6 months ago to no avail. Apparently there are complexities when it comes to Solaris x86 and 2.05b, and readline/gettext problems with 3.0). The problem with using keychain is that it needs to be run on the CLIENT system (where your SSH client is). keychain does not exist for Windows. The problem with the third site mentioned is that it has things which, simply put, do not work: (re: .screenrc modifications which "trick" screen into re-reading .screenrc on a re-attach; this doesn't work). I'd like end-users to discuss all of this, and figure out a good solution for this problem. I believe that there can be framework added to GNU screen to alleviate this entire ordeal once and for all. Thanks. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. | From MAILER-DAEMON Sun Feb 13 08:04:42 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D0JQW-0003m2-MP for mharc-screen-users@gnu.org; Sun, 13 Feb 2005 08:04:40 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D0JQS-0003kC-P5 for screen-users@gnu.org; Sun, 13 Feb 2005 08:04:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D0JQO-0003jB-9O for screen-users@gnu.org; Sun, 13 Feb 2005 08:04:33 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D0JJ8-0001uY-Qd for screen-users@gnu.org; Sun, 13 Feb 2005 07:57:02 -0500 Received: from [131.188.34.40] (helo=faui40.informatik.uni-erlangen.de) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D0InP-0002Lu-IW for screen-users@gnu.org; Sun, 13 Feb 2005 07:24:15 -0500 Received: (from mlschroe@localhost) by faui40.informatik.uni-erlangen.de (8.9.3p3/8.1.49-FAU) id NAA08701 for screen-users@gnu.org; Sun, 13 Feb 2005 13:24:13 +0100 (MET) Date: Sun, 13 Feb 2005 13:24:13 +0100 From: Michael Schroeder To: screen-users@gnu.org Message-ID: <20050213122413.GA6680@immd4.informatik.uni-erlangen.de> References: <20050213032958.GA89618@parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050213032958.GA89618@parodius.com> User-Agent: Mutt/1.4.2.1i Subject: Re: screen and ssh agents + agent forwarding X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 13:04:38 -0000 On Sat, Feb 12, 2005 at 07:29:58PM -0800, Jeremy Chadwick wrote: > I'd like end-users to discuss all of this, and figure out a good > solution for this problem. I believe that there can be framework added > to GNU screen to alleviate this entire ordeal once and for all. I don't think it makes sense to support ssh-agents outside of the screen session, as you can't modify the environment of the shells running in screen and thus screen would have to provide a kind of forwarding machanism. But what happens if you reattach with no ssh-agent? Or reattach multiple times with different ssh agents? Therefore you should start the ssh-agent in screen so that it doesn't die if you detach and use a fixed socket location. Cheers, Michael. -- Michael Schroeder mlschroe@informatik.uni-erlangen.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} From MAILER-DAEMON Wed Feb 16 16:59:36 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D1XCq-00034B-E2 for mharc-screen-users@gnu.org; Wed, 16 Feb 2005 16:59:36 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D1XCn-00033A-JX for screen-users@gnu.org; Wed, 16 Feb 2005 16:59:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D1XCl-00032A-AU for screen-users@gnu.org; Wed, 16 Feb 2005 16:59:31 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D1XCk-00031O-Lp for screen-users@gnu.org; Wed, 16 Feb 2005 16:59:30 -0500 Received: from [24.25.9.101] (helo=ms-smtp-02-eri0.southeast.rr.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D1Wx4-0005gY-Di for screen-users@gnu.org; Wed, 16 Feb 2005 16:43:18 -0500 Received: from [66.57.70.100] (rdu57-70-100.nc.rr.com [66.57.70.100]) by ms-smtp-02-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id j1GLhEed005446 for ; Wed, 16 Feb 2005 16:43:15 -0500 (EST) Message-ID: <4213BE6F.6020302@mailcan.com> Date: Wed, 16 Feb 2005 16:43:11 -0500 From: "Thomas G. Mayfield" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: screen-users@gnu.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: $LS_COLORS X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 21:59:34 -0000 I've hacked my $LS_COLORS to the exact point I like it, and when I login to my box, get just what I want. However, screen is somehow overwriting this variable. I've tried manually setting $LS_COLORS using 'setenv LS_COLORS ', and still it's wrong. For an example, I added the following two lines to my .screenrc: setenv FOO $LS_COLORS setenv LS_COLORS $LS_COLORS After screen starts up, however, $FOO and $LS_COLORS ($FOO, of course being my hacked version, and $LS_COLORS being the system default). I've looked through my .bashrc and .bash_profile, but the only entries they contain regarding $LS_COLORS are my own--to set it to the custom values. Any ideas? --Thomas G. Mayfield From MAILER-DAEMON Thu Feb 17 06:10:48 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D1jMg-0000P4-As for mharc-screen-users@gnu.org; Thu, 17 Feb 2005 05:58:34 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D1jIl-0008Tz-UQ for screen-users@gnu.org; Thu, 17 Feb 2005 05:54:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D1jIO-0008TE-6g for screen-users@gnu.org; Thu, 17 Feb 2005 05:54:25 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D1jIE-0008Si-Q0 for screen-users@gnu.org; Thu, 17 Feb 2005 05:54:00 -0500 Received: from [131.188.34.40] (helo=faui40.informatik.uni-erlangen.de) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D1j4l-0004ey-O9 for screen-users@gnu.org; Thu, 17 Feb 2005 05:40:04 -0500 Received: (from mlschroe@localhost) by faui40.informatik.uni-erlangen.de (8.9.3p3/8.1.49-FAU) id LAA11059; Thu, 17 Feb 2005 11:39:58 +0100 (MET) Date: Thu, 17 Feb 2005 11:39:58 +0100 From: Michael Schroeder To: "Thomas G. Mayfield" Message-ID: <20050217103958.GB8692@immd4.informatik.uni-erlangen.de> References: <4213BE6F.6020302@mailcan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4213BE6F.6020302@mailcan.com> User-Agent: Mutt/1.4.2.1i Cc: screen-users@gnu.org Subject: Re: $LS_COLORS X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 10:58:30 -0000 On Wed, Feb 16, 2005 at 04:43:11PM -0500, Thomas G. Mayfield wrote: > I've hacked my $LS_COLORS to the exact point I like it, and when I login > to my box, get just what I want. However, screen is somehow overwriting > this variable. I've tried manually setting $LS_COLORS using 'setenv > LS_COLORS ', and still it's wrong. > > For an example, I added the following two lines to my .screenrc: > setenv FOO $LS_COLORS > setenv LS_COLORS $LS_COLORS > > After screen starts up, however, $FOO and $LS_COLORS ($FOO, of course > being my hacked version, and $LS_COLORS being the system default). I've > looked through my .bashrc and .bash_profile, but the only entries they > contain regarding $LS_COLORS are my own--to set it to the custom values. > > Any ideas? Check out /etc/bash.bashrc and /etc/profile. (Your .bash_profile will nor be read if the shell is not a "login" shell, so you should set LS_COLORS in ~.bashrc.) Cheers, Michael. -- Michael Schroeder mlschroe@informatik.uni-erlangen.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} From MAILER-DAEMON Thu Feb 17 15:55:51 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D1sgh-00059k-0R for mharc-screen-users@gnu.org; Thu, 17 Feb 2005 15:55:51 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D1sgM-000555-O6 for screen-users@gnu.org; Thu, 17 Feb 2005 15:55:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D1sg5-00050C-Hl for screen-users@gnu.org; Thu, 17 Feb 2005 15:55:15 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D1sg4-0004wJ-En for screen-users@gnu.org; Thu, 17 Feb 2005 15:55:12 -0500 Received: from [24.25.9.101] (helo=ms-smtp-02-eri0.southeast.rr.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D1sKO-0001XB-8v for screen-users@gnu.org; Thu, 17 Feb 2005 15:32:48 -0500 Received: from [66.57.70.100] (rdu57-70-100.nc.rr.com [66.57.70.100]) by ms-smtp-02-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id j1HKWied011605 for ; Thu, 17 Feb 2005 15:32:45 -0500 (EST) Message-ID: <4214FF69.1040309@mailcan.com> Date: Thu, 17 Feb 2005 15:32:41 -0500 From: "Thomas G. Mayfield" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: screen-users@gnu.org References: <4213BE6F.6020302@mailcan.com> <20050217103958.GB8692@immd4.informatik.uni-erlangen.de> In-Reply-To: <20050217103958.GB8692@immd4.informatik.uni-erlangen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: $LS_COLORS X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 20:55:48 -0000 Michael Schroeder wrote: > On Wed, Feb 16, 2005 at 04:43:11PM -0500, Thomas G. Mayfield wrote: > >>I've hacked my $LS_COLORS to the exact point I like it, and when I login >>to my box, get just what I want. However, screen is somehow overwriting >>this variable. I've tried manually setting $LS_COLORS using 'setenv >>LS_COLORS ', and still it's wrong. >> >>For an example, I added the following two lines to my .screenrc: >>setenv FOO $LS_COLORS >>setenv LS_COLORS $LS_COLORS >> >>After screen starts up, however, $FOO and $LS_COLORS ($FOO, of course >>being my hacked version, and $LS_COLORS being the system default). I've >>looked through my .bashrc and .bash_profile, but the only entries they >>contain regarding $LS_COLORS are my own--to set it to the custom values. >> >>Any ideas? > > > Check out /etc/bash.bashrc and /etc/profile. (Your .bash_profile will > nor be read if the shell is not a "login" shell, so you should set > LS_COLORS in ~.bashrc.) > > Cheers, > Michael. > Mea culpa. Noticed that screen sets its own $TERM and just had to add "TERM screen" to the top of /etc/DIR_COLORS. Sorry to have wasted your time. --Thoma From MAILER-DAEMON Fri Feb 18 11:07:02 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D2Aej-0007kD-6t for mharc-screen-users@gnu.org; Fri, 18 Feb 2005 11:07:01 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D2Aea-0007hH-5q for screen-users@gnu.org; Fri, 18 Feb 2005 11:06:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D2AeU-0007ei-Re for screen-users@gnu.org; Fri, 18 Feb 2005 11:06:47 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D2AeU-0007dw-IZ for screen-users@gnu.org; Fri, 18 Feb 2005 11:06:46 -0500 Received: from [216.148.227.85] (helo=rwcrmhc12.comcast.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D2AOr-0005JH-FJ for screen-users@gnu.org; Fri, 18 Feb 2005 10:50:37 -0500 Received: from durin.aperiodic.net (pcp01840557pcs.owngsm01.md.comcast.net[68.32.120.226]) by comcast.net (rwcrmhc12) with ESMTP id <2005021815503301400hlc4de>; Fri, 18 Feb 2005 15:50:33 +0000 Received: from mithrandir.aperiodic.net (mithrandir.aperiodic.net [192.168.1.192]) by durin.aperiodic.net (Postfix) with ESMTP id 2FC0B384006 for ; Fri, 18 Feb 2005 10:50:32 -0500 (EST) Received: by mithrandir.aperiodic.net (Postfix, from userid 1000) id D20153B76CC6; Fri, 18 Feb 2005 10:50:31 -0500 (EST) Date: Fri, 18 Feb 2005 10:50:31 -0500 From: Phil!Gregory To: screen-users@gnu.org Message-ID: <20050218155029.GA1626@mithrandir.aperiodic.net> Mail-Followup-To: screen-users@gnu.org References: <20050213032958.GA89618@parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050213032958.GA89618@parodius.com> User-Agent: Mutt/1.5.6+20040907i Subject: Re: screen and ssh agents + agent forwarding (+ $DISPLAY) X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 16:06:54 -0000 * Jeremy Chadwick [2005-02-12 19:29 -0800]: > Anyone here who has tried to use GNU screen alongside an ssh agent > will know how painful it is to get things to work properly, especially > when using the forwarding mechanism of ssh agents. It's a complete > mess. I've thought about this before, and some more now. Here are my thoughts, with something of a solution following (skip the next paragraph if you don't want to read my ramblings on the subject): ssh agent information is maintained as environment variables. Michael points out that screen cannot modify its children's environments after spawning, so any solution will have to involve shells fixing themselves. screen should be updated, too, so that new children will get the most current values (unless you simply don't want to worry about non-shell windows). The hard part then becomes choosing the correct agent. This can be managed easily if you don't multi-attach, and semi-easily if you multi-attach but never use multiple displays simultaneously (e.g. you go to work, 'screen -x', use screen, and then detach before you go home). Once you start switching displays while leaving them attached, though, I don't see a way for anything to track what to do. Only screen knows which display input is currently coming from, and there's no way for anything to get that information from screen or for screen to tell anyone. And the most pathological case involves someone starting to type a command from one display, then finishing it and pressing enter from a different one. So, as I see it, the best approach is: when you start screen from an ssh session, have it note and record the necessary information, indexed by $SSH_CLIENT; keep track of your current "location", when that changes, you run a command that changes the location; have the shell check the location periodically and update its environment if the location changes. Details for my particular setup (and not only is this just for my stable of programs, I done a minimum of testing; YMMVG): I already use a wrapper script for starting screen, so in that script goes: if [ "$SSH_CLIENT" != "" ]; then IDXHOST=`echo $SSH_CLIENT | cut -d ' ' -f 1` mkdir -p ~/.screen/$IDXHOST/ ln -sf $SSH_AUTH_SOCK ~/.screen/$IDXHOST/ssh-auth-sock ln -sf ~/.screen/$IDXHOST/ssh-auth-sock ~/.ssh-auth-sock SSH_AUTH_SOCK=~/.ssh-auth-sock else IDXHOST=`hostname -i` mkdir -p ~/.screen/$IDXHOST/ fi echo $DISPLAY > ~/.screen/$IDXHOST/display cp ~/.screen/$IDXHOST/display ~/.display Then there's the setloc shell script: #!/bin/sh local LOCATION=$1 if [ "$STY" = "" ]; then echo "Not running in screen." 1>&2 exit 1 fi if [ ! -d ~/.screen/$LOCATION ]; then echo "There's no state recorded for $LOCATION." 1>&2 exit 1 fi if [ ! -e ~/.screen/$LOCATION/ssh-auth-sock ]; then echo "That SSH session appears to have gone away." 1>&2 exit 1 fi ln -sf ~/.screen/$LOCATION/ssh-auth-sock ~/.ssh-auth-sock cp ~/.screen/$LOCATION/display ~/.display And, finally, the shell's correction function. I use zsh, so the best place for this is in my preexec(). bash users will have to put it in $PROMPT_COMMAND, and the change won't take effect until a new prompt has been displayed after the change. (With zsh and preexec(), I can do setloc in one window then switch to another, run a program there, and have it work properly.): preexec () { if [ "$STY" != "" -a "$DISPLAY" != "`cat ~/.display`" ]; then DISPLAY=`cat ~/.display` fi } You can make symlinks in ~/.screen/ for more symbolic names, so you can e.g. run 'setloc work' instead of 'setloc 127.126.128.134' or whatever. -- ...computer contrarian of the first order... / http://aperiodic.net/phil/ PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 --- -- Girls are like internet domain names, the ones I like are already taken. well, you can stil get one from a strange country :-P -- geekissues.org quote #369 ---- --- -- From MAILER-DAEMON Fri Feb 18 15:58:37 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D2FCu-00038c-U2 for mharc-screen-users@gnu.org; Fri, 18 Feb 2005 15:58:37 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D2FCs-00036R-E8 for screen-users@gnu.org; Fri, 18 Feb 2005 15:58:34 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D2FCp-00034v-Sb for screen-users@gnu.org; Fri, 18 Feb 2005 15:58:33 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D2FCp-00034s-O7 for screen-users@gnu.org; Fri, 18 Feb 2005 15:58:31 -0500 Received: from [204.127.198.39] (helo=rwcrmhc13.comcast.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D2EzI-0002LR-Ki for screen-users@gnu.org; Fri, 18 Feb 2005 15:44:32 -0500 Received: from durin.aperiodic.net (pcp01840557pcs.owngsm01.md.comcast.net[68.32.120.226]) by comcast.net (rwcrmhc13) with ESMTP id <2005021820443101500l3fg2e>; Fri, 18 Feb 2005 20:44:31 +0000 Received: from mithrandir.aperiodic.net (mithrandir.aperiodic.net [192.168.1.192]) by durin.aperiodic.net (Postfix) with ESMTP id DE90E384006 for ; Fri, 18 Feb 2005 15:44:29 -0500 (EST) Received: by mithrandir.aperiodic.net (Postfix, from userid 1000) id 7B0DD3B76CC6; Fri, 18 Feb 2005 15:44:29 -0500 (EST) Date: Fri, 18 Feb 2005 15:44:29 -0500 From: Phil!Gregory To: screen-users@gnu.org Message-ID: <20050218204428.GB1626@mithrandir.aperiodic.net> Mail-Followup-To: screen-users@gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Subject: Bug Report: caption always + blanker X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 20:58:35 -0000 I'm still not sure what the best method of submitting a bug report is, so I'll shoot this out here. If you use 'caption always' and subsequently invoke 'blanker', the caption will still be drawn on screen when it changes (for example, if you have %C in the caption). This somewhat reduces the usefulness of a blanker, and tends to mess up the screen if another program has been set with 'blankerprg'. If you use 'hardstatus lastline' instead of 'caption always', the problem does not occur (the hardstatus is not drawn). A workaround would certainly be to switch to using the hardstatus, but I use (and like) the xterm title bar hardstatus hack, which leaves just the caption to use as a status bar. -- ...computer contrarian of the first order... / http://aperiodic.net/phil/ PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 --- -- Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (4) How many times do we have to tell you, "No prior art!" (3) Ha, ha, I can't believe they're actually going to adopt this sucker. ---- --- -- From MAILER-DAEMON Fri Feb 25 05:28:42 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D4ci7-0002M9-Ir for mharc-screen-users@gnu.org; Fri, 25 Feb 2005 05:28:40 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D4chx-0002LP-VM for screen-users@gnu.org; Fri, 25 Feb 2005 05:28:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D4chv-0002L0-0B for screen-users@gnu.org; Fri, 25 Feb 2005 05:28:27 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D4cfT-0001d4-Vk for screen-users@gnu.org; Fri, 25 Feb 2005 05:25:56 -0500 Received: from [142.104.105.206] (helo=saltspring.csc.uvic.ca) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D4cD2-0002Qz-If for screen-users@gnu.org; Fri, 25 Feb 2005 04:56:32 -0500 Received: from tsunami.abez.ca (S01060060676712c2.gv.shawcable.net [24.69.52.124]) (authenticated bits=0) by saltspring.csc.uvic.ca (8.12.10/8.12.8) with ESMTP id j1P9u5Cw030356 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 25 Feb 2005 01:56:14 -0800 Received: from tsunami.abez.ca (tsunami.abez.ca [127.0.0.1]) by tsunami.abez.ca (8.12.8/8.12.8) with ESMTP id j1P9twvi018836 for ; Fri, 25 Feb 2005 01:55:58 -0800 Date: Fri, 25 Feb 2005 01:55:58 -0800 (PST) From: abez To: screen-users@gnu.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-CS-Spam-Score: 1 (*) CS_VGA_10 X-CS-Spam-Status: No X-Scanned-By: MIMEDefang 2.41 Subject: Screen History + Questions X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2005 10:28:32 -0000 Screen seems like a rather stable project. I was viewing the mailinglist and noticed some maintainer movement but not much. I also noticed the Yahoo group devel is closed and dead. I have a few questions: How are the screen sources managed? I noticed the CVS was empty, all I see is the files in the FTP. How long has screen been around? I saw files older than 1995 in the FTP archive but that was version 3! What is the protocol for submitting patches to screen or discussing how to fix certain bugs. For instance I submitted a patch to Savanah regarding an SSH disconnect bug but I know it doesn't fix ALL of the SSH disconnect bugs (which basically is the SSH daemon not responding and not sending the right signals and thus a screen session totally hangs on reattach (blocking writes/reads)). Will this patch be noticed or is there a different way to submit it. How do the maintainers talk with each other? Is it all through this list? Anyways I love screen and I really must thank you guys for the hard work. abram -- abez ------------------------------------------ http://www.abez.ca/ Abram Hindle (abez@abez.ca) ------------------------------------------ abez From MAILER-DAEMON Fri Feb 25 06:26:27 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D4dc1-0003wB-UN for mharc-screen-users@gnu.org; Fri, 25 Feb 2005 06:26:26 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D4dbv-0003s1-GP for screen-users@gnu.org; Fri, 25 Feb 2005 06:26:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D4dbo-0003lL-HR for screen-users@gnu.org; Fri, 25 Feb 2005 06:26:14 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D4dbn-0003id-2p for screen-users@gnu.org; Fri, 25 Feb 2005 06:26:11 -0500 Received: from [131.188.34.40] (helo=faui40.informatik.uni-erlangen.de) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D4dMY-0008OY-CB for screen-users@gnu.org; Fri, 25 Feb 2005 06:10:26 -0500 Received: (from mlschroe@localhost) by faui40.informatik.uni-erlangen.de (8.9.3p3/8.1.49-FAU) id MAA19009; Fri, 25 Feb 2005 12:10:12 +0100 (MET) Date: Fri, 25 Feb 2005 12:10:12 +0100 From: Michael Schroeder To: abez Message-ID: <20050225111012.GA16477@immd4.informatik.uni-erlangen.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: screen-users@gnu.org Subject: Re: Screen History + Questions X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2005 11:26:23 -0000 On Fri, Feb 25, 2005 at 01:55:58AM -0800, abez wrote: > How are the screen sources managed? I noticed the CVS was empty, all I see > is the files in the FTP. Yes, Juergen wants to sync the CVS, but hasn't found the time to do it yet. > How long has screen been around? I saw files older than 1995 in the FTP > archive but that was version 3! The screen project was started 1987 by Oliver Lauman, Juergen and myself started working on it in 1990. > What is the protocol for submitting patches to screen or discussing how > to fix certain bugs. Mail to this mailing list or screen@uni-erlangen.de. > For instance I submitted a patch to Savanah > regarding an SSH disconnect bug but I know it doesn't fix ALL of the SSH > disconnect bugs (which basically is the SSH daemon not responding and > not sending the right signals and thus a screen session totally hangs on > reattach (blocking writes/reads)). Will this patch be noticed or is > there a different way to submit it. Hmm, I think I missed it. > How do the maintainers talk with each other? Is it all through this > list? Yes. Cheers, Michael. -- Michael Schroeder mlschroe@informatik.uni-erlangen.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} From MAILER-DAEMON Fri Feb 25 19:02:08 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D4pPL-0003X0-Jh for mharc-screen-users@gnu.org; Fri, 25 Feb 2005 19:02:08 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D4pPI-0003Ux-FR for screen-users@gnu.org; Fri, 25 Feb 2005 19:02:05 -0500 Received: from mailman by lists.gnu.org with local (Exim 4.43) id 1D4pPF-0003Tk-SG for screen-users@gnu.org; Fri, 25 Feb 2005 19:02:01 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D4pFb-0007sO-25 for screen-users@gnu.org; Fri, 25 Feb 2005 18:52:03 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D4pFZ-0007nS-PF for screen-users@gnu.org; Fri, 25 Feb 2005 18:52:01 -0500 Received: from [195.149.224.23] (helo=smtp.djeden.kei.pl) by monty-python.gnu.org with smtp (Exim 4.34) id 1D4os8-0007Cu-Kl for screen-users@gnu.org; Fri, 25 Feb 2005 18:27:49 -0500 Received: (qmail 5125 invoked by uid 700); 25 Feb 2005 23:27:52 -0000 Received: from 249.77.classcom.pl (HELO ninikowo) (postmaster@dominik.kei.pl@195.150.77.249) by 23.224.149.195.tld.pl with SMTP; 25 Feb 2005 23:27:52 -0000 From: "Dominik" To: "screen-users@gnu.org" Date: Fri, 25 Feb 2005 23:50:29 +0100 (CET) Priority: Normal X-Mailer: PMMail 2.20.2382 for OS/2 Warp 4.5 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Message-Id: X-TMDA-Confirmed: Fri Feb 25 19:02:01 EST 2005 Subject: size + refresh + cursor position + logfile position X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dominik List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2005 00:02:05 -0000 Hi Can I get actual window size of detached screen? How can refresh all content of screen actual window and insert all this to logfile? I just want to get everything what's in screen actual window. is this possible to get somehow where is cursor in actual screen position? I want to send to screen something via stuff command but don't know where it will be placed, I know I can do this by sending for example " (backspace)" but maybe there's better way to do this trick :) One thing more, I can't set up logfiles position, I want to have them somehow in actual directory, hardcopy I can set by hardcopydir command, but it dosn't work with this one. TIA :) CU -- Dominik Chmaj _| _ o o |_ GG: 919564 www.dominik.kei.pl (_| (_) (\/) | (\) | |\ ICQ: 101929211 From MAILER-DAEMON Fri Feb 25 19:02:10 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D4pPM-0003Xd-JA for mharc-screen-users@gnu.org; Fri, 25 Feb 2005 19:02:09 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D4pPJ-0003Vu-Cn for screen-users@gnu.org; Fri, 25 Feb 2005 19:02:05 -0500 Received: from mailman by lists.gnu.org with local (Exim 4.43) id 1D4pPH-0003UJ-4I for screen-users@gnu.org; Fri, 25 Feb 2005 19:02:03 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D4pFb-0007sO-25 for screen-users@gnu.org; Fri, 25 Feb 2005 18:52:03 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D4pFZ-0007nS-PF for screen-users@gnu.org; Fri, 25 Feb 2005 18:52:01 -0500 Received: from [195.149.224.23] (helo=smtp.djeden.kei.pl) by monty-python.gnu.org with smtp (Exim 4.34) id 1D4os8-0007Cu-Kl for screen-users@gnu.org; Fri, 25 Feb 2005 18:27:49 -0500 Received: (qmail 5125 invoked by uid 700); 25 Feb 2005 23:27:52 -0000 Received: from 249.77.classcom.pl (HELO ninikowo) (postmaster@dominik.kei.pl@195.150.77.249) by 23.224.149.195.tld.pl with SMTP; 25 Feb 2005 23:27:52 -0000 From: "Dominik" To: "screen-users@gnu.org" Date: Fri, 25 Feb 2005 23:50:29 +0100 (CET) Priority: Normal X-Mailer: PMMail 2.20.2382 for OS/2 Warp 4.5 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Message-Id: X-TMDA-Confirmed: Fri Feb 25 19:02:03 EST 2005 Subject: size + refresh + cursor position + logfile position X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dominik List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2005 00:02:05 -0000 Hi Can I get actual window size of detached screen? How can refresh all content of screen actual window and insert all this to logfile? I just want to get everything what's in screen actual window. is this possible to get somehow where is cursor in actual screen position? I want to send to screen something via stuff command but don't know where it will be placed, I know I can do this by sending for example " (backspace)" but maybe there's better way to do this trick :) One thing more, I can't set up logfiles position, I want to have them somehow in actual directory, hardcopy I can set by hardcopydir command, but it dosn't work with this one. TIA :) CU -- Dominik Chmaj _| _ o o |_ GG: 919564 www.dominik.kei.pl (_| (_) (\/) | (\) | |\ ICQ: 101929211 From MAILER-DAEMON Sat Feb 26 11:54:34 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D55D7-0006Ey-QL for mharc-screen-users@gnu.org; Sat, 26 Feb 2005 11:54:33 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D55D4-0006Cy-JY for screen-users@gnu.org; Sat, 26 Feb 2005 11:54:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D55Ch-000644-8G for screen-users@gnu.org; Sat, 26 Feb 2005 11:54:08 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D55Ce-0005js-OS for screen-users@gnu.org; Sat, 26 Feb 2005 11:54:06 -0500 Received: from [82.182.133.20] (helo=pc18.dolda2000.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D54pp-0001Zy-OW for screen-users@gnu.org; Sat, 26 Feb 2005 11:30:30 -0500 Received: from 2002:52b6:8514:200:20c:76ff:fe3b:a3f4 ([IPv6:2002:52b6:8514:200:20c:76ff:fe3b:a3f4]) (authenticated bits=0) by pc18.dolda2000.com (8.13.1/8.13.1) with ESMTP id j1QGUQrO021500 for ; Sat, 26 Feb 2005 17:30:27 +0100 From: Fredrik Tolf To: screen-users@gnu.org Content-Type: text/plain Date: Sat, 26 Feb 2005 17:30:26 +0100 Message-Id: <1109435426.15302.60.camel@pc7.dolda2000.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit Subject: [PATCH] Kerberos support for screen X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2005 16:54:31 -0000 Hi all! I was having some trouble with Kerberos and screen, so I wrote this patch. Not sure if I should send patches to "screen-users", but I couldn't find any other mailing list. =) Anyway, my basic problems were two: 1. If one logs in with Kerberos support and thereby gets tickets and then starts a screen, that screen session will use the same credential cache. If one then detaches the screen and logs out, the login program will remove the credential cache, and the processes running in the detached screen will be ticket-less. Therefore, this patch makes a copy of the credential cache and ensures that all processes in the screen session will use it. 2. If I start a screen, detach it and let it lie for some time, the tickets will expire if I don't manually log in once in a while and renew them manually. Therefore, this patch renews the tickets when necessary (it registers an event that runs once per minute and examines if it's time to renew the tickets, and does so if it deems it good). If you apply the patch, you'll need to run configure with --with-krb5 (no auto-detection is done). It requires either MIT Krb5 or a compliant API (I think it should support Heimdal, but I haven't tried, so I don't know). The patch (and two auxiliary patches) is available at . I tried to send this mail with the patch attached at first, but it crossed the message size limit of the list. I'd be glad if this appears in a future version of screen, so that I don't have to patch it manually for much longer. ;-) I hope it helps someone. Fredrik Tolf From MAILER-DAEMON Sat Feb 26 12:52:18 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D566z-000536-Bl for mharc-screen-users@gnu.org; Sat, 26 Feb 2005 12:52:17 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D566o-0004zv-1X for screen-users@gnu.org; Sat, 26 Feb 2005 12:52:06 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D566h-0004xD-7z for screen-users@gnu.org; Sat, 26 Feb 2005 12:52:00 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D566g-0004s0-Qd for screen-users@gnu.org; Sat, 26 Feb 2005 12:51:58 -0500 Received: from [64.233.170.196] (helo=rproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D55Yn-0004Wb-AU for screen-users@gnu.org; Sat, 26 Feb 2005 12:16:57 -0500 Received: by rproxy.gmail.com with SMTP id c16so754003rne for ; Sat, 26 Feb 2005 09:16:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=lEK0I6+nogdCvzVVg7Qyj8imLgOpmpi5DnamCR/c/IgqprGrpMubAL+ZAQsQ5v48BnxUIQr+ajDgBTto02NyI+7zB1jYyxlPx+K3FP9ZcVTLx4uNRb2NBPL0xNwjDf1xlxHAoAenaFBJGanSUDMJzo2KLA9/bqEN3Uzd89JMarE= Received: by 10.38.67.1 with SMTP id p1mr411914rna; Sat, 26 Feb 2005 09:16:56 -0800 (PST) Received: by 10.38.207.2 with HTTP; Sat, 26 Feb 2005 09:16:56 -0800 (PST) Message-ID: Date: Sat, 26 Feb 2005 11:16:56 -0600 From: inode0 To: screen-users@gnu.org In-Reply-To: <1109435426.15302.60.camel@pc7.dolda2000.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1109435426.15302.60.camel@pc7.dolda2000.com> Subject: Re: [PATCH] Kerberos support for screen X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: inode0 List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2005 17:52:11 -0000 On Sat, 26 Feb 2005 17:30:26 +0100, Fredrik Tolf wrote: > Hi all! > > I was having some trouble with Kerberos and screen, so I wrote this > patch. Not sure if I should send patches to "screen-users", but I > couldn't find any other mailing list. =) I've been dealing with these issues for a long time too but I didn't perceive it to be a problem with screen. > Anyway, my basic problems were two: > 1. If one logs in with Kerberos support and thereby gets tickets and > then starts a screen, that screen session will use the same credential > cache. If one then detaches the screen and logs out, the login program > will remove the credential cache, and the processes running in the > detached screen will be ticket-less. Therefore, this patch makes a copy > of the credential cache and ensures that all processes in the screen > session will use it. I put my credential cache in a location where it won't be deleted either by configuring kerberos to do that by default or by setting the appropriate environment variables. That seems to solve this problem for me. > 2. If I start a screen, detach it and let it lie for some time, the > tickets will expire if I don't manually log in once in a while and renew > them manually. Therefore, this patch renews the tickets when necessary > (it registers an event that runs once per minute and examines if it's > time to renew the tickets, and does so if it deems it good). This one is more philosophical to me. The situations where I'm using screen/kerberos together tend to be on fairly secure machines where I'm comfortable leaving long tickets sitting on the machine. Renewing them is a bit annoying, but doing that once a month hasn't been that annoying to me. Maybe I just haven't quite made the mental adjustment going from krb4 philosophy to krb5 yet? John From MAILER-DAEMON Sat Feb 26 15:53:10 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D58w1-0002nt-Vm for mharc-screen-users@gnu.org; Sat, 26 Feb 2005 15:53:10 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D58vr-0002im-VL for screen-users@gnu.org; Sat, 26 Feb 2005 15:53:00 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D58vd-0002d2-Fi for screen-users@gnu.org; Sat, 26 Feb 2005 15:52:54 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D58vb-0002YS-Bd for screen-users@gnu.org; Sat, 26 Feb 2005 15:52:43 -0500 Received: from [82.182.133.20] (helo=pc18.dolda2000.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D58bG-0005J9-0l for screen-users@gnu.org; Sat, 26 Feb 2005 15:31:42 -0500 Received: from 2002:52b6:8514:200:20c:76ff:fe3b:a3f4 ([IPv6:2002:52b6:8514:200:20c:76ff:fe3b:a3f4]) (authenticated bits=0) by pc18.dolda2000.com (8.13.1/8.13.1) with ESMTP id j1QKVTAZ022274; Sat, 26 Feb 2005 21:31:29 +0100 From: Fredrik Tolf To: inode0 In-Reply-To: References: <1109435426.15302.60.camel@pc7.dolda2000.com> Content-Type: text/plain Date: Sat, 26 Feb 2005 21:31:29 +0100 Message-Id: <1109449889.15302.71.camel@pc7.dolda2000.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit Cc: screen-users@gnu.org Subject: Re: [PATCH] Kerberos support for screen X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2005 20:53:03 -0000 On Sat, 2005-02-26 at 11:16 -0600, inode0 wrote: > On Sat, 26 Feb 2005 17:30:26 +0100, Fredrik Tolf wrote: > > Hi all! > > > > I was having some trouble with Kerberos and screen, so I wrote this > > patch. Not sure if I should send patches to "screen-users", but I > > couldn't find any other mailing list. =) > > I've been dealing with these issues for a long time too but I didn't > perceive it to be a problem with screen. Well, neither did I. I just perceived that screen would be a good place to fix it. It's also a question of semantics to me. In my opinion, you're supposed to have one ccache per session, and since screen in essence creates a new session, I think the correct semantic is to have screen manage a ccache for that session. > > Anyway, my basic problems were two: > > 1. If one logs in with Kerberos support and thereby gets tickets and > > then starts a screen, that screen session will use the same credential > > cache. If one then detaches the screen and logs out, the login program > > will remove the credential cache, and the processes running in the > > detached screen will be ticket-less. Therefore, this patch makes a copy > > of the credential cache and ensures that all processes in the screen > > session will use it. > > I put my credential cache in a location where it won't be deleted > either by configuring kerberos to do that by default or by setting the > appropriate environment variables. That seems to solve this problem > for me. Yeah, but then you actually have to put your ccache in a different location, manually. That's what I wanted to avoid. :) IMHO, everything that can be automated should be, so that's what I did. > > 2. If I start a screen, detach it and let it lie for some time, the > > tickets will expire if I don't manually log in once in a while and renew > > them manually. Therefore, this patch renews the tickets when necessary > > (it registers an event that runs once per minute and examines if it's > > time to renew the tickets, and does so if it deems it good). > > This one is more philosophical to me. The situations where I'm using > screen/kerberos together tend to be on fairly secure machines where > I'm comfortable leaving long tickets sitting on the machine. Renewing > them is a bit annoying, but doing that once a month hasn't been that > annoying to me. Maybe I just haven't quite made the mental adjustment > going from krb4 philosophy to krb5 yet? Again, I think that everything that can be automated should be, so I decided to automate it and make screen renew the tickets. Also, I'm not very comfortable with long-lived tickets. Maybe it's just me, but I feel much better having tickets that can be renewed for a long time, but that expire sooner. My tickets expire after 10 hrs, but are renewable for 10 days. Either way, I don't intend to shove the patch down your throat. ;-) I just found it useful, and posted it 1) in the hope that someone else finds it useful, and 2) it the hope that it might make it into the next release of screen, so that I don't have to patch my machines manually anymore. Fredrik Tolf From MAILER-DAEMON Sat Feb 26 16:56:31 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D59vL-0000Ok-Ju for mharc-screen-users@gnu.org; Sat, 26 Feb 2005 16:56:31 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D59vK-0000OK-AO for screen-users@gnu.org; Sat, 26 Feb 2005 16:56:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D59pj-00081E-M7 for screen-users@gnu.org; Sat, 26 Feb 2005 16:50:49 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D59pf-0007ni-GK for screen-users@gnu.org; Sat, 26 Feb 2005 16:50:39 -0500 Received: from [64.233.170.206] (helo=rproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D59Hq-0007ou-Ns for screen-users@gnu.org; Sat, 26 Feb 2005 16:15:42 -0500 Received: by rproxy.gmail.com with SMTP id c16so772823rne for ; Sat, 26 Feb 2005 13:15:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Yrl4xrXtLADf1MpYE2Mti3s92OqZr/ddDSDuO0pKwMIIOg3TcXXrJWDqcOK9Jtp86ylB6dMqrJ4n0hqlmvFPjEOCEBt/c58bW6+e1XFuFAHliq/wy7wc1ONM6YQB+cwybWPQzwKzRFV/RQw82NSM+xKWe/wDXR1bvEbwyTfMaDA= Received: by 10.38.76.59 with SMTP id y59mr94659rna; Sat, 26 Feb 2005 13:15:42 -0800 (PST) Received: by 10.38.207.2 with HTTP; Sat, 26 Feb 2005 13:15:42 -0800 (PST) Message-ID: Date: Sat, 26 Feb 2005 15:15:42 -0600 From: inode0 To: screen-users@gnu.org In-Reply-To: <1109449889.15302.71.camel@pc7.dolda2000.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1109435426.15302.60.camel@pc7.dolda2000.com> <1109449889.15302.71.camel@pc7.dolda2000.com> Subject: Re: [PATCH] Kerberos support for screen X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: inode0 List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2005 21:56:30 -0000 On Sat, 26 Feb 2005 21:31:29 +0100, Fredrik Tolf wrote: > On Sat, 2005-02-26 at 11:16 -0600, inode0 wrote: > > > > I put my credential cache in a location where it won't be deleted > > either by configuring kerberos to do that by default or by setting the > > appropriate environment variables. That seems to solve this problem > > for me. > > Yeah, but then you actually have to put your ccache in a different > location, manually. That's what I wanted to avoid. :) > IMHO, everything that can be automated should be, so that's what I did. On machines where I am the sole user, I build kerberos to use a non-standard default location and don't run kdestroy at logout. Otherwise, I set KRB5CCNAME and KRBTKFILE during login. I don't do anything manually during the normal course of events. I agree though that is not well suited to all situations. I just offered it as the way I went about getting around this problem. I didn't mean that it was a better way, just another way. > > This one is more philosophical to me. The situations where I'm using > > screen/kerberos together tend to be on fairly secure machines where > > I'm comfortable leaving long tickets sitting on the machine. Renewing > > them is a bit annoying, but doing that once a month hasn't been that > > annoying to me. Maybe I just haven't quite made the mental adjustment > > going from krb4 philosophy to krb5 yet? > > Again, I think that everything that can be automated should be, so I > decided to automate it and make screen renew the tickets. Also, I'm not > very comfortable with long-lived tickets. Maybe it's just me, but I feel > much better having tickets that can be renewed for a long time, but that > expire sooner. My tickets expire after 10 hrs, but are renewable for 10 > days. I certainly share your discomfort with long tickets in many circumstances. I am comfortable with them on machines that aren't public and that I'm logged into constantly anyway. And those are the machines I typically leave screen sessions hanging around on. This, I think, may be the spot where I just haven't gotten used to the idea of renewable tickets yet. That may well be a better way to go. > Either way, I don't intend to shove the patch down your throat. ;-) Oh, I have no objection to your proposed patch. I also don't have any say in whether it is accepted. Just trying to share what I've been doing to work around the same issues, although my situation may well be sufficiently different from others that it isn't useful in general. Best wishes Fredrik. I heartily applaud you for contributing something of substance that involves two of my favorite things! John From MAILER-DAEMON Sat Feb 26 18:23:01 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D5BH1-0003yQ-E7 for mharc-screen-users@gnu.org; Sat, 26 Feb 2005 18:23:00 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D5BGx-0003wx-Ej for screen-users@gnu.org; Sat, 26 Feb 2005 18:22:55 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D5BGs-0003uW-AF for screen-users@gnu.org; Sat, 26 Feb 2005 18:22:51 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5BGr-0003tI-LC for screen-users@gnu.org; Sat, 26 Feb 2005 18:22:49 -0500 Received: from [64.62.145.229] (helo=mx1.parodius.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D5B0q-000526-Ch for screen-users@gnu.org; Sat, 26 Feb 2005 18:06:16 -0500 Received: from pentarou.parodius.com (localhost [127.0.0.1]) by mx1.parodius.com (8.13.1/8.13.1) with ESMTP id j1QN6Wh2099219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 26 Feb 2005 15:06:32 -0800 (PST) (envelope-from jdc@pentarou.parodius.com) Received: (from jdc@localhost) by pentarou.parodius.com (8.13.1/8.13.1/Submit) id j1QN6WEm099218 for screen-users@gnu.org; Sat, 26 Feb 2005 15:06:32 -0800 (PST) (envelope-from jdc) Date: Sat, 26 Feb 2005 15:06:32 -0800 From: Jeremy Chadwick To: screen-users@gnu.org Message-ID: <20050226230632.GA99108@parodius.com> Mail-Followup-To: screen-users@gnu.org References: <1109435426.15302.60.camel@pc7.dolda2000.com> <1109449889.15302.71.camel@pc7.dolda2000.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1109449889.15302.71.camel@pc7.dolda2000.com> User-Agent: Mutt/1.5.8i Subject: Re: [PATCH] Kerberos support for screen X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2005 23:22:57 -0000 Fredrik, Can this sort-of logic (re: screen keeping one credential cache for Kerberos) be applied to the situation pertaining to SSH agents? (see my previous thread on the gnu-screen mailing list for details) The solution you've proposed sounds, to me, like a good one. I think we all agree it's not the "responsibility" of screen to solve problems like these, but there's really no other place it can be solved while using screen itself. Framework for solving this problem, in my opinion, is a Good Thing(tm). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. | On Sat, Feb 26, 2005 at 09:31:29PM +0100, Fredrik Tolf wrote: > On Sat, 2005-02-26 at 11:16 -0600, inode0 wrote: > > On Sat, 26 Feb 2005 17:30:26 +0100, Fredrik Tolf wrote: > > > Hi all! > > > > > > I was having some trouble with Kerberos and screen, so I wrote this > > > patch. Not sure if I should send patches to "screen-users", but I > > > couldn't find any other mailing list. =) > > > > I've been dealing with these issues for a long time too but I didn't > > perceive it to be a problem with screen. > > Well, neither did I. I just perceived that screen would be a good place > to fix it. It's also a question of semantics to me. In my opinion, > you're supposed to have one ccache per session, and since screen in > essence creates a new session, I think the correct semantic is to have > screen manage a ccache for that session. > > > > Anyway, my basic problems were two: > > > 1. If one logs in with Kerberos support and thereby gets tickets and > > > then starts a screen, that screen session will use the same credential > > > cache. If one then detaches the screen and logs out, the login program > > > will remove the credential cache, and the processes running in the > > > detached screen will be ticket-less. Therefore, this patch makes a copy > > > of the credential cache and ensures that all processes in the screen > > > session will use it. > > > > I put my credential cache in a location where it won't be deleted > > either by configuring kerberos to do that by default or by setting the > > appropriate environment variables. That seems to solve this problem > > for me. > > Yeah, but then you actually have to put your ccache in a different > location, manually. That's what I wanted to avoid. :) > IMHO, everything that can be automated should be, so that's what I did. > > > > 2. If I start a screen, detach it and let it lie for some time, the > > > tickets will expire if I don't manually log in once in a while and renew > > > them manually. Therefore, this patch renews the tickets when necessary > > > (it registers an event that runs once per minute and examines if it's > > > time to renew the tickets, and does so if it deems it good). > > > > This one is more philosophical to me. The situations where I'm using > > screen/kerberos together tend to be on fairly secure machines where > > I'm comfortable leaving long tickets sitting on the machine. Renewing > > them is a bit annoying, but doing that once a month hasn't been that > > annoying to me. Maybe I just haven't quite made the mental adjustment > > going from krb4 philosophy to krb5 yet? > > Again, I think that everything that can be automated should be, so I > decided to automate it and make screen renew the tickets. Also, I'm not > very comfortable with long-lived tickets. Maybe it's just me, but I feel > much better having tickets that can be renewed for a long time, but that > expire sooner. My tickets expire after 10 hrs, but are renewable for 10 > days. > > Either way, I don't intend to shove the patch down your throat. ;-) > I just found it useful, and posted it 1) in the hope that someone else > finds it useful, and 2) it the hope that it might make it into the next > release of screen, so that I don't have to patch my machines manually > anymore. > > Fredrik Tolf > > > > _______________________________________________ > screen-users mailing list > screen-users@gnu.org > http://lists.gnu.org/mailman/listinfo/screen-users From MAILER-DAEMON Sat Feb 26 19:23:44 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D5CDn-0002sM-Kb for mharc-screen-users@gnu.org; Sat, 26 Feb 2005 19:23:43 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D5CDi-0002qv-GI for screen-users@gnu.org; Sat, 26 Feb 2005 19:23:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D5CDg-0002qC-DT for screen-users@gnu.org; Sat, 26 Feb 2005 19:23:37 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5CCe-0002MS-RX for screen-users@gnu.org; Sat, 26 Feb 2005 19:22:32 -0500 Received: from [82.182.133.20] (helo=pc18.dolda2000.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D5BsG-0007jY-Uf for screen-users@gnu.org; Sat, 26 Feb 2005 19:01:29 -0500 Received: from 2002:52b6:8514:200:20c:76ff:fe3b:a3f4 ([IPv6:2002:52b6:8514:200:20c:76ff:fe3b:a3f4]) (authenticated bits=0) by pc18.dolda2000.com (8.13.1/8.13.1) with ESMTP id j1R01L14022973; Sun, 27 Feb 2005 01:01:22 +0100 From: Fredrik Tolf To: inode0 In-Reply-To: References: <1109435426.15302.60.camel@pc7.dolda2000.com> <1109449889.15302.71.camel@pc7.dolda2000.com> Content-Type: text/plain Date: Sun, 27 Feb 2005 01:01:21 +0100 Message-Id: <1109462482.15302.101.camel@pc7.dolda2000.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit Cc: screen-users@gnu.org Subject: Re: [PATCH] Kerberos support for screen X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 00:23:39 -0000 On Sat, 2005-02-26 at 15:15 -0600, inode0 wrote: > On Sat, 26 Feb 2005 21:31:29 +0100, Fredrik Tolf wrote: > > Either way, I don't intend to shove the patch down your throat. ;-) > > Oh, I have no objection to your proposed patch. I also don't have any > say in whether it is accepted. Just trying to share what I've been > doing to work around the same issues, although my situation may well > be sufficiently different from others that it isn't useful in general. I'm sorry if I sounded overly aggressive -- I know that you didn't mean to object. However, when you said that you "didn't perceive it to be a problem with screen", you struck at the heart of something I hadn't really considered -- there _isn't_ really a problem with screen. There's no obvious reason why screen should have to be extended to cover for problems with Kerberos, after all. I guess it's a compromise in one of two directions: 1. Either one agrees with my argument that a screen back-end constitutes a session in itself and therefore should take care to manage its own credential cache in a Kerberos-enabled system. 2. One goes with the other argument that my patch is extending screen with tasks that screen shouldn't have to bother with in the first place, and argues to fix either Kerberos itself or the system integration with Kerberos (for example, associating each process with a kernel-level credential cache would solve this problem as well, and arguable in a nicer way as well -- you'd get automatic credential cache garbage collection, automatic renewal and who knows what more) Now, to be sure: My patch may well not be the best way to go. However, to my knowledge, it's the only currently implemented way to go. The latest versions of the Linux kernel have had an option called CONFIG_KEYS, described as "This option provides support for retaining authentication tokens and access keys in the kernel...", so maybe they're rooting for a kernel-level credential cache. If that is so, then it will probably solve the problem on a better level. Until then, however, there's little choice to my knowledge. Of course, I could be completely wrong altogether in my assessment, so please comment. :-) I've also committed the patch to the Gentoo Linux and Fedora Core bugzillas, so I'll see what they have to say about it. > Best wishes Fredrik. I heartily applaud you for contributing something > of substance that involves two of my favorite things! I'm glad that you, too, see Kerberos that way. Many people that I talk to seem to see Kerberos as some kind of necessary evil, which makes me a bit sad considering how beautiful it is. :-) Fredrik Tolf From MAILER-DAEMON Sat Feb 26 19:51:32 2005 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1D5Ceh-0004YZ-RS for mharc-screen-users@gnu.org; Sat, 26 Feb 2005 19:51:31 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D5Ccq-0003Zo-D4 for screen-users@gnu.org; Sat, 26 Feb 2005 19:49:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D5Cci-0003XG-JI for screen-users@gnu.org; Sat, 26 Feb 2005 19:49:29 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5Cci-0003Po-3Z for screen-users@gnu.org; Sat, 26 Feb 2005 19:49:28 -0500 Received: from [82.182.133.20] (helo=pc18.dolda2000.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D5CBE-0000Ir-8l for screen-users@gnu.org; Sat, 26 Feb 2005 19:21:05 -0500 Received: from 2002:52b6:8514:200:20c:76ff:fe3b:a3f4 ([IPv6:2002:52b6:8514:200:20c:76ff:fe3b:a3f4]) (authenticated bits=0) by pc18.dolda2000.com (8.13.1/8.13.1) with ESMTP id j1R0L2ID023089 for ; Sun, 27 Feb 2005 01:21:02 +0100 From: Fredrik Tolf Cc: screen-users@gnu.org In-Reply-To: <20050226230632.GA99108@parodius.com> References: <1109435426.15302.60.camel@pc7.dolda2000.com> <1109449889.15302.71.camel@pc7.dolda2000.com> <20050226230632.GA99108@parodius.com> Content-Type: text/plain Date: Sun, 27 Feb 2005 01:21:01 +0100 Message-Id: <1109463661.15302.116.camel@pc7.dolda2000.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit Subject: Re: [PATCH] Kerberos support for screen X-BeenThere: screen-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General GNU Screen discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 00:51:30 -0000 On Sat, 2005-02-26 at 15:06 -0800, Jeremy Chadwick wrote: > Fredrik, > > Can this sort-of logic (re: screen keeping one credential cache for > Kerberos) be applied to the situation pertaining to SSH agents? (see my > previous thread on the gnu-screen mailing list for details) > > The solution you've proposed sounds, to me, like a good one. I think > we all agree it's not the "responsibility" of screen to solve problems > like these, but there's really no other place it can be solved while > using screen itself. Framework for solving this problem, in my opinion, > is a Good Thing(tm). As you say, these two problems are very similar in nature. If you want my honest opinion, stop using ssh-agent and use Kerberos instead. ;-) If you, as I suspect, don't want to do that, however, your problem can be solved very similarly. However, it cannot be solved as completely as with Kerberos. The ssh-agent is similar to the Kerberos credential cache in that they both act as a sort of key cache. However, Kerberos' ccache resides locally on each machine you're logged in to, while ssh-agent run on the machine you initially logged in to. In other words, there's only one copy of the ssh-agent, while there can be an arbitrary number of copies of Kerberos ccaches. If I were to propose a solution to your problem, it would be to have the screen back-end create a new socket, export its path in the SSH_AUTH_SOCK to all subshells (like I do with the KRB5CCNAME variable), and then proxy all connections to that socket, through the screen front-end (attacher), to the ssh-agent auth sock that the attacher has access to. However, since, like I mentioned, ssh-agent runs on the machine that you initially logged in to, there is simply no way let the processes running in the screen session have access to an ssh-agent while the screen is detached and you're not logged in to the machine where it's running, whereas the Kerberos ccache can simply be copied and kept by the screen back-end. That may or may not be a problem for you. If it is, however, then I see no other choice for you than to switch to Kerberos (which you should do either way, though ;-) ). Fredrik Tolf