On 2014-03-07 19:52, Jan Larres wrote: > Are you seeing the sleep jobs in the 'Jobs:' output of 'tmux info'?
Ah, yes, I do see them in my case. > I didn't have any jobs there, but I don't know how to test it at the > moment since as I mentioned that section seems to be missing from my > info output in the current tmux revision. The code is still there, just the output mechanism changed a bit: If you don't have jobs, then nothing is printed. Just try "tmux run -b 'sleep 30'; tmux info" and you'll see one. > > running the server under "valgrind --track-fds=yes" > That sounds like an interesting idea, I'll have a look at that. Yes, and also add something like --log-file=~/valgrind.log to the arguments. Do this when you can afford to restart your server. It might slow down tmux but we get valuable logs in return. When you see too many open fds already, quit the server and if all goes well (tmux doesn't close them) then valgrind will dump the backtraces of their creation. Don't forget to create a debug build of tmux before doing this! -- Balazs ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
