Kill it with -9 and then run tmux -, kill and new tmux again and
look for the logs in the current directory.
On Sun, Feb 27, 2011 at 07:49:28AM +0530, Vaibhav Bedia wrote:
> On Sat, Feb 26, 2011 at 9:11 PM, Nicholas Marriott
> wrote:
> >
> > what platform? linux at a guess?
> Yes linux.
> >
On Sun, Feb 27, 2011 at 2:53 PM, Nicholas Marriott
wrote:
> Kill it with -9 and then run tmux -, kill and new tmux again and
> look for the logs in the current directory.
I am unable to kill it.
$kill -9 7988
$pgrep -l -u tmux
I see pid for tmux i.e. 7988 listed again.
So i ran the followi
D state is noninterruptible disk so either a) it is in the middle of
coring or writing a log file b) it is writing to NFS or another file
system which has vanished c) your kernel has a bug.
If it doesn't vanish in a while then either forget about it or reboot.
Then try rm -R /tmp/tmux-* then do
On Mon, Feb 28, 2011 at 2:35 AM, Nicholas Marriott
wrote:
> D state is noninterruptible disk so either a) it is in the middle of
> coring or writing a log file b) it is writing to NFS or another file
> system which has vanished c) your kernel has a bug.
I finally got it to work :)
I specified a
