-
Notifications
You must be signed in to change notification settings - Fork 468
Description
I sometimes have so many active sessions (>200 panes total) that I run into (apparent) memory problems indicated by random "server exited unexpectedly" errors. At which point I'm forced to delete windows and sessions, which destroys state that tmux-resurrect would be able to store, just not on a per-session basis (unless I'm missing something).
If you say I should just use fewer session to avoid this, I'd argue that doing so would partially defeat the purpose of tmux-session. You'll run into OOM situations almost inevitably after some amount of heavy tmux-resurrect usage because tmux-resurrect encourages you to never close sessions, as you can just have them saved and restored for you. So as long as you want to use different sessions for different pieces of work, you'll eventually run into the problem that you have too many sessions open for the tmux server to handle.
So what I'd like to have is an ability to save and delete individual sessions and restore them individually later. Is this feasible? It would raise the question what to do with those "saved" sessions during a normal resurrect-restore. Probably you'd need to remember for each session whether it was last open or saved/persisted.
Ideally I'd then also automate this further and automatically save and delete sessions that haven't been active for a while, but this might be out of scope for tmux-resurrect and can probably be scripted externally or as part of something like tmux-continuum easy enough.