From owner-freebsd-questions@FreeBSD.ORG Sat Dec 19 01:03:16 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BDDD10656B5 for ; Sat, 19 Dec 2009 01:03:16 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from mx.utwente.nl (mx2.utsp.utwente.nl [130.89.2.13]) by mx1.freebsd.org (Postfix) with ESMTP id C6D518FC1B for ; Sat, 19 Dec 2009 01:03:15 +0000 (UTC) Received: from nox-laptop.student.utwente.nl (nox-laptop.student.utwente.nl [130.89.170.109]) by mx.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id nBJ12r9e021085; Sat, 19 Dec 2009 02:02:53 +0100 From: Pieter de Goeje To: freebsd-questions@freebsd.org Date: Sat, 19 Dec 2009 02:02:51 +0100 User-Agent: KMail/1.9.10 References: <20091218183418.GB15899@guilt.hydra> In-Reply-To: <20091218183418.GB15899@guilt.hydra> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200912190202.52600.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact icts.servicedesk@utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: Chad Perrin Subject: Re: broken tmux X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 01:03:16 -0000 On Friday 18 December 2009 19:34:18 Chad Perrin wrote: > When I tried asking this before, it was evidently during a period that > the mailing list was down, so I'll try again: > > After updating software on a FreeBSD 6.1 system, tmux appears to be > broken. I still have a persistent tmux session running on the system, > but I cannot access it with `tmux att`. I also cannot start new tmux > sessions. > > As a non-root user: > > tmux att > > can't create socket: Not a directory > > > tmux > > can't create socket: Not a directory > What happens if you do "tmux -S /some/path/tmuxsocket", detach, and then "tmux -S /some/path/tmuxsocket a"? If that works then there is some problem with the default socket path (/tmp/tmux-####). I would check the permissions on /tmp and remove any /tmp/tmux* directories. -- Pieter de Goeje