Date: Tue, 10 Jun 2014 16:58:30 +0200 From: Oliver Brandmueller <ob@e-Gitt.NET> 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> In-Reply-To: <alpine.BSF.2.00.1406101320100.14243@mail.fig.ol.no> References: <alpine.BSF.2.00.1406101320100.14243@mail.fig.ol.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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. |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140610145829.GA1642>