From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 14:58:34 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5DAB7B72 for ; Tue, 10 Jun 2014 14:58:34 +0000 (UTC) Received: from main.mx.e-gitt.net (service.rules.org [IPv6:2001:1560:2342::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1D7742F1A for ; Tue, 10 Jun 2014 14:58:33 +0000 (UTC) Received: from ob by main.mx.e-gitt.net with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1WuNVO-000LIW-5U for freebsd-stable@freebsd.org; Tue, 10 Jun 2014 16:58:30 +0200 Date: Tue, 10 Jun 2014 16:58:30 +0200 From: Oliver Brandmueller To: freebsd-stable@freebsd.org Subject: Re: sysutils/screen switched from using named pipes to local domain sockets Message-ID: <20140610145829.GA1642@e-Gitt.NET> Mail-Followup-To: freebsd-stable@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Face: "TT~P'b_)-jKU_0^a=usXryz`YTz)z.[FZrI,A~PREI2U}frrZ`>_J&; ^t|^.dR/mqtC,Vb.Y>~u8(|aL)vAv(k">zY"]*m*y|b8S7:WK[/qP5i>HO#Ek; C[X:b|FP0*Ly_4Ni User-Agent: Mutt/1.5.23 (2014-03-12) Sender: Oliver Brandmueller X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2014 14:58:34 -0000 On Tue, Jun 10, 2014 at 01:36:12PM +0200, Trond Endrestøl wrote: > Maybe a heads-up is in order. > > If you're in the (bad?) habit of running portupgrade, etc, from > sysutils/screen, beware that screen 4.2.1 switched from using named > pipes to local domain sockets. The naming of sockets hasn't changed, > only the (file) type. > > Stop any running screen sessions before upgrading sysutils/screen, or > perhaps you should upgrade your ports while in single-user mode. That alos seems to break connecting to another user's shared screen session: user a has in his .screenrc acladd b When user b now trys: screen -x a/ seteuid: Operation not permitted [...] seteuid: Operation not permitted Illegal instruction So there's more going wrong with this update, careful if you rely on this funtionality. - Oliver -- | Oliver Brandmueller http://sysadm.in/ ob@sysadm.in | | Ich bin das Internet. Sowahr ich Gott helfe. |