Skip to content

PocketShell v1.6.1

Choose a tag to compare

View all tags
@Big-Pony Big-Pony released this 30 Jul 14:14
v1.6.1
74632e7

PocketShell v1.6.1

修复

  • Linux 上应用内更新失败：v1.6.0 的 install 子命令把二进制装在 root 拥有的 /usr/local/bin，而服务以你自己的用户身份运行。更新时需在二进制旁写临时文件再原子替换，要求的是目录写权限，因此失败并报 EACCES: permission denied, copyfile '…' -> '/usr/local/bin/.pocketshell.new'。本版把二进制改放 /opt/pocketshell/（归服务用户所有），/usr/local/bin/pocketshell-agent 变为指向它的符号链接，命令仍在全局 PATH 上，sudo pocketshell-agent uninstall 照常可用。macOS 不受此问题影响（LaunchAgent 装在用户目录下，本就有写权限）。

升级

已安装 v1.6.0 的，在服务器上重跑一次安装命令即可迁移，密钥目录不受影响、已配对的手机不掉线：

sudo pocketshell-agent install --advertise wss://your.domain --name 我的服务器

PocketShell v1.6.1

Fixed

  • In-app updates failed on Linux: the install subcommand shipped in v1.6.0 put the binary in root-owned /usr/local/bin while running the service as your own user. An update writes a temporary file next to the binary and renames it into place, so it needs write access to the directory — hence EACCES: permission denied, copyfile '…' -> '/usr/local/bin/.pocketshell.new'. The binary now lives in /opt/pocketshell/, owned by the service user, and /usr/local/bin/pocketshell-agent is a symlink pointing at it, so the command stays on the global PATH and sudo pocketshell-agent uninstall keeps working. macOS was never affected — a LaunchAgent installs under your home directory, which you can already write.

Upgrade

If you already installed v1.6.0, re-run the install command on your server to migrate. Your key directory is untouched and paired phones stay paired:

sudo pocketshell-agent install --advertise wss://your.domain --name my-server
Assets 7
Loading