rjyo/osewa v0.1.5

osewa v0.1.5

on GitHub

Several users can each run osewa on one host, ~. hands the session to
your next attach, and attach --new starts a session of its own.

• Several users on one host. Each user runs their own server, and
  every one wanted port 7322, so a second user's login failed with "can't
  be reached". When another user's server already holds 7322, login now
  gives this user's server the next free port (7323 and up), keeps it in
  ~/.config/osewa/port on the host, and records it on your machine.
  A host already on 7322 keeps it. When the port reaches another user's
  server, login now says so. (#11)
• ~. gives up ownership. Each osewa attach is a new client, so
  attaching again within 30 s of a detach made you a viewer of "another
  window on this device". ~. now gives up ownership at once. A
  dropped connection still keeps it for 30 s. Inside ssh, type ~~.:
  ssh passes one ~ on, and osewa detaches.
  (#12)
• osewa attach --new <host> starts a session and attaches to it,
  even when others are running. attach with no id still joins the only
  running session. (#14)
• QUIC no longer spins on a broken socket. A socket whose reads kept
  failing had them retried in a tight loop, keeping a CPU core busy. The
  connection now ends after repeated failures and redials.
• Normal CPU priority on macOS. The launchd agent now runs as an
  interactive process, so osewa shells get the same CPU priority as ssh
  or mosh. Existing installs pick this up on the next
  osewa service install.

~. giving up ownership needs this release on both ends; the port
choice needs it on the host. This release interoperates with v0.1.4
(p0-s1).