oh yeah lock can do strange things. its weird, i thought it was when you kill its terminal but it doesn't block SIGHUP so that shouldn't be it
if you'd killed lock then tmux would probably have been okay see if you can reproduce, preferably with -current cheers On Thu, Feb 03, 2011 at 04:18:48PM -0500, Darryl Wisneski wrote: > On Thu, Feb 03, 2011 at 08:35:31PM +0000, Nicholas Marriott wrote: > > never seen it before, can you reproduce with -current? > > > > you can attach gdb to it and see what its up to > > Nick: > > I will do my best to get to -current. > > FYI. Before I killed the server (before I read this so I didn't > attach gdb) I noticed that an attached xterm on the fvwm was looping > on the lock, asking for key. I killed that xterm and then I could > run "tmux ls" and get all the session info. But when I ran "tmux > attach-session t -o". It was hung again. That's when I gave up > and killed it. Even after that I noticed in top that a "lock" > process was running. > > Thanks, > -dkw > > > > > > > On Wed, Feb 02, 2011 at 03:08:41PM -0500, Darryl Wisneski wrote: > > > Howdy: > > > > > > I believe I have a hung tmux server. "tmux ls" does not return any > > > data and hangs the shell. I can't run any commands against tmux > > > without my shell hanging. My OS is obsd 4.8 with base tmux being > > > used. I have about 20 windows on session group 0 and 6 windows on > > > another session group 1. The server is still running. > > > > > > load averages: 1.36, 1.21, 1.15 > > > 332 processes: 1 running, 329 idle, 1 stopped, 1 on processor > > > CPU states: 2.4% user, 0.0% nice, 0.3% system, 0.0% interrupt, 97.3% > > > idle > > > Memory: Real: 551M/926M act/tot Free: 62M Swap: 74M/1024M used/tot > > > > > > PID USERNAME PRI NICE SIZE RES STATE WAIT TIME CPU > > > COMMAND > > > 22463 dkw 64 0 8868K 8392K run - 223:35 95.36% tmux > > > > > > ktrace shows a lock or loop, waiting... > > > > > > 22463 tmux CALL getpid() > > > 22463 tmux RET getpid 22463/0x57bf > > > > > > I wonder if I can generate a core, else if other users are experiencing > > > similar issues sometimes. > > > > > > Thanks, > > > -dkw > > > > > > > > > ------------------------------------------------------------------------------ > > > The modern datacenter depends on network connectivity to access resources > > > and provide services. The best practices for maximizing a physical > > > server's > > > connectivity to a physical network are well understood - see how these > > > rules translate into the virtual world? > > > http://p.sf.net/sfu/oracle-sfdevnlfb > > > _______________________________________________ > > > tmux-users mailing list > > > tmux-users@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/tmux-users > > > > ------------------------------------------------------------------------------ > > The modern datacenter depends on network connectivity to access resources > > and provide services. The best practices for maximizing a physical server's > > connectivity to a physical network are well understood - see how these > > rules translate into the virtual world? > > http://p.sf.net/sfu/oracle-sfdevnlfb > > _______________________________________________ > > tmux-users mailing list > > tmux-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/tmux-users ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
