Yes but in my case it is just a safety killing, if the tmux with the exact
matching name exists I want to kill it but if it is not exactly the same I
want to let it work.
When a machine is launched, as I often use the same names, if some kind of
zombi with the same name exists I like to be sure to
Yes you should check "tmux ls" to see if the exact session you want is
there.
On Thu, Jun 28, 2012 at 03:04:35PM -0500, clow...@clownix.net wrote:
>
> Yes but in my case it is just a safety killing, if the tmux with the exact
> matching name exists I want to kill it but if it is not exactly the
If there is only one session that could possibly match "cloo" tmux picks
it because it must be the one you mean, there is no alternative. If
there was any doubt, then it doesn't. For example:
$ tmux kill-server
$ tmux new -ds clooA
$ tmux new -ds clooB
$ tmux kill-session -t cloo
more than one ses
I was wrong:
Cloonix destroys any machine with the same name before starting a tmux.
do:
tmux new-session -s cloon -d /bin/bash
tmux list-session
tmux kill-session -t cloo
tmux list-session
You can understand that creating the cloo machine destroys the cloon machine
One letter is missing in th
On 28 June 2012 14:19, wrote:
>
> Hello
> I have replaced in cloonix (a software launching virtual machines) screen
> with tmux, I am very happy about it, but there is a small bug in the
> names we can choose:
>
> my software does: "tmux new-session -s name_cloonix_machine -d exe_cloonix"
>
> If
