Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restoring and Multiple Servers #365

Open
SamuelLarkin opened this issue Oct 23, 2020 · 4 comments
Open

Restoring and Multiple Servers #365

SamuelLarkin opened this issue Oct 23, 2020 · 4 comments

Comments

@SamuelLarkin
Copy link

Hi,
I have a use case where I need two tmux servers. I would start the second server by tmux -L CentOs7 new -s myjob. The issue I'm having is that the second server tries to restore the first server's session which is NOT what I want. Is there a way to have multiple servers with their separate save/restore?

@bruno-
Copy link
Member

bruno- commented Oct 24, 2020

Hi,
this plugin does not have the awareness of socket name (CentOs7 in tmux -L CentOs7). When you perform restore it just restores the last saved session from any tmux server.

@samm81
Copy link

samm81 commented May 9, 2021

hi, I am also interested in this feature!

digging around, it looks like modifying resurrect_file_path to append the socket path (tmux display-message -p -F "#{socket_path}") could bring us 80% of the way there

is this the right direction?

I suppose you'd also need multple last links, one for each socket ?

@strogonoff
Copy link

strogonoff commented Jul 7, 2023

@samm81 I’m not sure multiple last links are required—if we simply use current socket as part of resurrect_dir (filename may be enough, since all sockets are in the same directory: basename $(tmux display-message -p -F "#{socket_path}")), that should cover everything? I might try it.

@strogonoff
Copy link

Done in #481, seems to work according to local testing on my machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants