Glad to hear your problem is solved. Cheers
Original message
From: c...@free.fr
Date: 30/03/2014 03:19 (GMT+00:00)
To: Nicholas Marriott
Cc: tmux-users@lists.sourceforge.net
Subject: Re : Re: Re : Re: Permissions on Sessions via Socket's permission --
20140328
Thank you Nicholas for your help, it makes things really easier.
now, about the version of tmux i used for the tests unfortunately it might be
too old
as it doesn't even provide the -V option.
So i turned to a more recent version (namely 1.6 according to -V) and repeated
the tests.
As you wrote,
What tmux version? I have a feeling I fixed something about changing the socket
perms
Original message
From: c...@free.fr
Date: 29/03/2014 00:21 (GMT+00:00)
To: Nicholas Marriott
Cc: tmux-users@lists.sourceforge.net
Subject: Re : Re: Permissions on Sessions via Socket&#
Thank very much Nicholas for your prompt and enlightning reply.
Though i'm sure any technical issues can be solved in due time
(like, in the case of sockets then if one is not enough, how about
two? so we can split function among them... Well i'm not developer
over here and lack the required bac
Both read and write permission is needed on the socket to attach and
this cannot be changed.
You can attach with -r (tmux attach -r) to attach readonly which is a
convenience to prevent accidental interference.
Do not give people you do not trust access to your tmux socket, readonly
or not.
On
Good Day everyone!
As a seli-starter with tmux, i'll expose my use case by a little scenario :
+ Beth is working on a project and wants to show it to Bob
+ but she doesn't want Bob to do anything on it (read only).
I thought i'd be able to achieve such a situation by using Sockets :
1. BETH
