client has nothing to do with forking children from status-interval, something is counting the stats wrong
so is this actually causing you a problem? On Tue, Oct 05, 2010 at 11:06:40AM +0200, marcel partap wrote: > On 05/10/10 09:09, Nicholas Marriott wrote: > >How do you mean? Are you saying the three processes you start once a > >second never exit? > Well at least to my limited understanding, no.. at least with htop or pstree > i can't see any child processes. However, using > dstat --top-io-adv -p > tmux quickly takes the lead on i/o and the new process count > constantly raises (in the case of status-interval 1, +1 per second), > taking more and more CPU aswell.. > > >Does it happen if you run them once every 30 seconds? > Too slow to notice. It happens with 3 seconds interval.. > Oh and btw, only the attached client process is affected, not the (detached) > server.. > > regards, marcel. ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
