Page MenuHomeDevCentral

Deploy tmux-reattach
ClosedPublic

Authored by dereckson on Mar 7 2023, 18:11.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 1, 22:23
Unknown Object (File)
Fri, Nov 1, 12:28
Unknown Object (File)
Thu, Oct 31, 14:07
Unknown Object (File)
Thu, Oct 31, 13:01
Unknown Object (File)
Wed, Oct 30, 09:07
Unknown Object (File)
Wed, Oct 30, 08:50
Unknown Object (File)
Sun, Oct 27, 03:54
Unknown Object (File)
Sat, Oct 26, 22:04
Subscribers
None

Details

Summary

It's in a lot of places, like in /root/bin for docker-001, but not everywhere.
Basically it's a small wrapper to reattach to tmux, and launch it when needed.

tmux 1.8 introduced the new-session command with a way to attach a session
if already existing, and we currently have 3.x deployed everywhere. That would
require a deterministic naming approach, to avoid the second fork command call.

So instead, we keep the old pre-1.8 solution to try to attach, and create
the new session when that fails.

Test Plan

tmux-reattach

Diff Detail

Repository
rOPS Nasqueron Operations
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

dereckson created this revision.

Alternative way: tmux new -AD -s some-session-name, so yup, seems a correct approach without naming sessions.

This revision is now accepted and ready to land.Mar 7 2023, 18:33
This revision was automatically updated to reflect the committed changes.