That was it. I just had to get rid of the "set -g default-command" that
used reattach-to-user-namespace. Thanks!
On Tue, Apr 23, 2013 at 3:31 AM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> It probably is. If you use sudo it doesn't use your .tmux.conf, it uses
> root's .tmux.conf.
It probably is. If you use sudo it doesn't use your .tmux.conf, it uses
root's .tmux.conf. Remove any default-command or default-shell options
from your .tmux.conf. tmux will not start if your default-command or
default-shell don't exist.
On Tue, Apr 23, 2013 at 03:23:37AM -0500, Mark Volkmann wr
I don't have that. It is looking for it because I just copied
.tmux.conf from my Mac. I don't think that's the issue though because
tmux starts fine if I start it with sudo. That's why I thought it was
an issue with a permission on some other file.
---
R. Mark Volkmann
Object Computing, Inc.
On A
Do you have reattach-to-user-namespace? Isn't that for OS X? Probably
your default-shell or default-command is wrong in .tmux.conf.
On Mon, Apr 22, 2013 at 07:33:04PM -0500, Mark Volkmann wrote:
>Thanks! That produces four files whose names begin with "strace.out.".
>There are around 20 o
Thanks! That produces four files whose names begin with "strace.out.".
There are around 20 open() failures across those files that all say "No
such file or directory".
I suspect all or most of these are expected errors for optional files.
Here they are:
/etc/ld.so.nohwcap
/tmp/tmux-1000/default
/e
Try "strace -ff -ostrace.out tmux new" then look for an open() that
fails in the output files. Send me the files if you can't figure it out
and I'll have a look.
On Mon, Apr 22, 2013 at 08:18:01AM -0500, Mark Volkmann wrote:
>I was able to install tmux on a Raspberry Pi running the recommende
