On Tue, May 11, 2010 at 03:02:00PM +0300, Lars Nooden wrote: > On Tue, 11 May 2010, Nicholas Marriott wrote: > > Yeah we should probably relax that to allow group permissions, try this. > > The patch itself allows tmux to tolerate a socket which has group read > write permissions allowed. In practice, tmux recreates the socket or > resets the permissions back to the old values so it only works once.
I'll have a look and see why this is happening when I have time. > Once tmux resets the permissions to 700, access is not possible from the > second account: > server not found: Permission denied > > > What if new-session could take an optional mode argument like mkdir? No I don't think we need any more options, things can just be group writable and tmux should not reset the permissions, so you can do eg tmux new -d && chgrp -R blah /tmp/tmux-`id -u`. > Letting the file system handle the permissions would be a fairly easy to > implement compromise. The default mode would be 700, but the user could > override that -- at least for the group permissions. > > > you can also make a hardlink to the socket if necessary. > > Good to know. I've ignored hardlinks till now. Thanks. > > /Lars > > ------------------------------------------------------------------------------ > > _______________________________________________ > tmux-users mailing list > tmux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tmux-users ------------------------------------------------------------------------------ _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
