Just a suggestion, but could you try running strace (or MacOSX's
equivalent) on tmux, and redirect the output to another computer,
something like this:
otherhost:
ncat -l -p 5678 2>&1 | tee tmux_log
localhost:
strace -f tmux 2>&1 | ncat otherhost 5678
Then you'd be able to see/tell us, roughly w
My thought is that the panic is in VFS so it could be a FS bug and you
might be able to avoid it by putting the tmux socket on a different FS.
Probably won't help though.
On Sun, Jul 24, 2011 at 06:45:56AM -0400, Chas. Owens wrote:
> On Sat, Jul 23, 2011 at 22:23, Tim Gray wrote:
> > On Jul 24,
