restart server

[LovesAsuna]

After updating tuios on the remote host, it’s necessary to run kill-server to apply the changes. However, when I access the remote host via tuios and execute this command, the connection gets terminated. I then have to manually SSH into the remote host and use attach or start-server to restore tuios functionality. I wonder if there’s any way to achieve “restarting the daemon and re-establishing the connection” directly while connected to the remote host through tuios—perhaps via a command like restart-server?

[sueun-dev]

For a [hosts] machine, v0.9.2 has hosts sync. Run it from the controller, outside the remote daemon you're stopping:

tuios hosts sync NAME --dry-run
tuios hosts sync NAME --restart

Sync targets the controller's version and can restart a daemon whose version differs, even when its binary on disk is already current. It requests confirmation when sessions exist. Running programs end and layouts return with new shells. If it's already stopped, tuios hosts test NAME --start starts it using the installed binary.

Are you using federated attach --host NAME, nested --ssh, or the built-in SSH server? Those paths matter for reconnecting. I ran the extracted restart script with synthetic tuios responses: kill-before-start and both failure paths passed. That covers the script, not SSH reconnection or session restoration.

[Gaurav-Gosain]

Hi, and thanks to @sueun-dev for the pointers. I will add what is missing.

You need to stop the daemon from outside the connection it serves. kill-server on the remote host ends the daemon that your tuios client is talking to, so the connection drops. Nothing is wrong with your setup.

If the host is in your [hosts] table, run this on your local machine:

tuios hosts sync NAME --restart

It saves every session, restarts the daemon on the host, and the layouts come back. Use --dry-run first to see the plan. It asks before it ends anything.

Two things to know about a restart:

• The layouts come back with new shells. The programs that ran in the panes end.
• kill-server writes the state of every session first, so a later tuios resurrect NAME or start-server brings the panes back.

If you only want to restart the daemon and not install anything, SSH to the host once and run tuios kill-server && tuios start-server. Then attach again. A restart-server command that does this from inside the connection is a fair idea. The client would need to reconnect on its own afterwards. I will think about it.

I am also working on a live upgrade of the daemon, so a new binary can take over without ending the programs in your panes. It is not released yet. When it lands, it should remove most of the reasons to restart.

Which kind of connection do you use: attach --host NAME, --ssh, or the SSH server? The answer changes what reconnecting looks like.

[LovesAsuna]

I use the command attach --host NAME. I prefer to update the tuos daemon via SSH because accessing GitHub from the Chinese network is often subject to timeouts. Therefore, I need to manually download and install the binary files, and then manually restart the server. If I were to use the sync command, I would likely get stuck during the download of the update files. So, I typically do it this way:

1. Attach to host NAME
2. Manually update the binary files.
3. Establish a new SSH connection to the server, then kill the server, and then restart the server.

[Gaurav-Gosain]

Thanks, that helps. Slow GitHub access changes the picture. There are two ways to cut out the second SSH login.

1. From your own machine, with the binary you already downloaded

tuios hosts sync NAME --binary ./tuios --restart

hosts sync never downloads anything on the host. It sends the file to the host over ssh, installs it, and restarts the daemon. With --binary, it doesn't touch GitHub at all. The file has to be built for the host's system, so use the same archive you'd copy over by hand. Add --dry-run first if you want to see the plan.

If your local tuios is already the same version as the one you installed on the host, a plain tuios hosts sync NAME --restart works too. It only fetches a release for a host whose binary is a different version, so in that case it just restarts the daemon. Be careful the other way round, though: sync installs the version of the machine you run it on. If your local tuios is older, it would put the older one back. --binary avoids that.

2. From inside the remote pane, after you replace the binary

setsid -f sh -c 'tuios kill-server; tuios start-server' >/dev/null 2>&1

A plain tuios kill-server && tuios start-server can't work from a pane. The kill ends the shell it runs in, so start-server never runs. setsid -f starts the pair outside the pane, so it survives the kill. I tried it on a test daemon. The daemon came back with the session restored, and as usual each pane got a new shell.

With attach --host, your client should keep the last frame on screen and redial on its own for up to three minutes, so it should reconnect when the new daemon is up. I tested the restart, but not the reconnect over a host link. If it doesn't come back for you, please tell me what you see.

That one-liner is basically what a restart-server command would do. If it works well for you, it's a good sign that wrapping it as a command is worth doing.