Ey guys,
I've been using sysutil/tmux a long time already but right now I'm seriously considering to move back to Screen because I've just about had it with all the weird stuff that surrounds it. I'm wasting way too much time over this.
It started a few versions back when I began noticing that TMux no longer kept the screen intact. I'm a heavy Midnight Commander user (misc/mc) and every time I'd switch sessions then several lines of the screen would disappear and a quick ^l would make them re-appear again. Slightly annoying, but I figured that it was just some weird change I should look into sometime.
So today I'm setting up a new server (Dell PowerEdge SC1420, should make a really nice BSD server), added my account ("peter") and copied my TMux configuration onto it (~/.tmux.conf). Logged on, started TMux but no configuration (ugly green status bar and it uses ^b vs. my standard ^a). Checked file permissions and all that, nothing.
I did a lot of testing and eventually started all over...
I added 2 new users. One is called peter and the other piet. Other than the name both are identical. Same shell, same group layout (own name + wheel) and both using the exact same .tmux.conf) (copied by root from /root/backup).
Guess what? If piet logs on and starts tmux, all is well. If peter logs on and starts tmux its configuration gets ignored.
I even backtraced it to this (I think):
Yet there is nothing wrong with the configuration file.
Then it hit me... what if... I changed my userid from 1001 to 1003 and all of a sudden it worked. So then I re-did my test again, but this time first created user piet (1001) and then peter (1002).
And all was normal.
Concluding: If you use TMux while using a username peter with userid 1001 then its configuration file won't be parsed.
Of course this behavior doesn't seem to be consistent. If I try the exact same thing on a virtual FreeBSD CURRENT (VirtuaBox) and pull in TMux from the repositories then peter/1001 works like a charm.
Either way, I've just about had it with TMux on FreeBSD.
I've been using sysutil/tmux a long time already but right now I'm seriously considering to move back to Screen because I've just about had it with all the weird stuff that surrounds it. I'm wasting way too much time over this.
It started a few versions back when I began noticing that TMux no longer kept the screen intact. I'm a heavy Midnight Commander user (misc/mc) and every time I'd switch sessions then several lines of the screen would disappear and a quick ^l would make them re-appear again. Slightly annoying, but I figured that it was just some weird change I should look into sometime.
So today I'm setting up a new server (Dell PowerEdge SC1420, should make a really nice BSD server), added my account ("peter") and copied my TMux configuration onto it (~/.tmux.conf). Logged on, started TMux but no configuration (ugly green status bar and it uses ^b vs. my standard ^a). Checked file permissions and all that, nothing.
I did a lot of testing and eventually started all over...
I added 2 new users. One is called peter and the other piet. Other than the name both are identical. Same shell, same group layout (own name + wheel) and both using the exact same .tmux.conf) (copied by root from /root/backup).
Guess what? If piet logs on and starts tmux, all is well. If peter logs on and starts tmux its configuration gets ignored.
I even backtraced it to this (I think):
Code:
fcntl(5,F_SETFL,O_RDWR|O_NONBLOCK) = 0 (0x0)
getpid() = 88089 (0x15819)
__getcwd("/home/peter",1024) = 0 (0x0)
ioctl(0,TIOCGETA,0x7fffffffdd50) = 0 (0x0)
ioctl(0,FIODGNAME,0x7fffffffdd60) = 0 (0x0)
close(2147483647) ERR#9 'Bad file descriptor'
fcntl(0,F_GETFL,) = 2 (0x2)
fcntl(0,F_SETFL,O_RDWR|O_NONBLOCK) = 0 (0x0)
dup(0x0) = 6 (0x6)
getpid() = 88089 (0x15819)
poll({ 3/POLLIN 5/POLLIN|POLLOUT },2,-1) = 1 (0x1)
sendmsg(5,0x7fffffffdbf0,0) = 113 (0x71)
close(6) = 0 (0x0)
Then it hit me... what if... I changed my userid from 1001 to 1003 and all of a sudden it worked. So then I re-did my test again, but this time first created user piet (1001) and then peter (1002).
And all was normal.
Concluding: If you use TMux while using a username peter with userid 1001 then its configuration file won't be parsed.
Of course this behavior doesn't seem to be consistent. If I try the exact same thing on a virtual FreeBSD CURRENT (VirtuaBox) and pull in TMux from the repositories then peter/1001 works like a charm.
Either way, I've just about had it with TMux on FreeBSD.