hmm is this something happening regularly with different servers or you
have one server here you are looking at?
On Wed, Sep 21, 2011 at 01:11:46PM +0200, marcel partap wrote:
> >This is weird
> indeed ^^
> >Can you send "tmux info" output?
> Yes we can C:
> tmux 1.6, pid 8196, started Sat Sep
This is weird
indeed ^^
Can you send "tmux info" output?
Yes we can C:
tmux 1.6, pid 8196, started Sat Sep 17 04:32:41 2011
socket path /tmp/tmux-0/default, debug level 0
system is Linux 3.1.0-rc4-00131-g9e79e3e #27 SMP PREEMPT Thu Sep 1 12:05:51
CEST 2011 x86_64
configuration file is /root/.t
This is weird, either epoll is returning EPOLLHUP but read() is
returning EAGAIN not 0 or an error, or epoll is returning EPOLLIN and
read() is always returning EAGAIN.
Can you send "tmux info" output?
On Tue, Sep 20, 2011 at 03:47:26PM +0200, marcel partap wrote:
> On 20/09/11 14:40, Nicholas M
tmux version? libevent version?
give the full strace log for 10 seconds please
On Tue, Sep 20, 2011 at 02:05:22PM +0200, marcel partap wrote:
> Hi there :)
> This is a strange thing, sometimes tmux totally pwns one CPU, just
> noticed it has been consuming bloody 30hours of precious 2.8GHz
> p
Hi there :)
This is a strange thing, sometimes tmux totally pwns one CPU, just
noticed it has been consuming bloody 30hours of precious 2.8GHz
processor time that should have been going to BOINC *grrr* ^^
anyways, a crude statistical analysis after detaching all clients
> sleep 10s && killall -v
