Page MenuHomeDevCentral

Deploy tmux-reattach
ClosedPublic

Authored by dereckson on Mar 7 2023, 18:11.
Tags
None
Referenced Files
F56416413: D2850.id7263.diff
Thu, Nov 5, 23:40
F56252752: D2850.id7263.diff
Wed, Nov 4, 06:21
F56239517: D2850.id7262.diff
Wed, Nov 4, 02:53
F56234336: D2850.id.diff
Wed, Nov 4, 01:37
F56096970: D2850.diff
Mon, Nov 2, 20:36
Unknown Object (File)
Sat, Oct 31, 00:13
Unknown Object (File)
Fri, Oct 30, 18:22
Unknown Object (File)
Wed, Oct 28, 05:19
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 Passed
Unit
No Test Coverage
Branch
main
Build Status
Buildable 4499
Build 4766: arc lint + arc unit

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.