Distillation

Date: Sep 8, 2026

• 🟡 (04:01) System inventory showed 159 loaded systemd units.
• 🟡 (04:01) Custom and network-facing services active/running included opencode.service (Opencode Server), light-match.service (indoor lighting automation), hostapd@2g.service, hostapd@5g.service, minidlna.service, tailscaled.service, ssh.service, smbd.service, nmbd.service, docker.service, and containerd.service.
• 🟡 (04:01) ts-opencode-advertise.service was loaded but inactive/dead; its description was “Ensure Tailscale svc:opencode is advertised.”
• 🟡 (04:01) Host networking used active/running systemd-networkd.service and systemd-resolved.service; NetworkManager.service was not found. ufw.service was loaded and active/exited, while firewalld.service was not found.
• 🟡 (04:01) auditd.service was not found. apparmor.service was loaded and active/exited.
• 🟡 (04:02) PTY implementation source contained exact limits MAX_SESSIONS_PER_OWNER = 5 and MAX_ARGUMENT_BYTES = 65_536; it also enforces MAX_SESSIONS, MAX_ARGUMENTS, and MAX_BUFFER_SIZE, though those values were not visible in the supplied excerpt.
• 🟡 (04:02) PTY implementation supports starting an interactive command in a background PTY, detached spawning (detached: true), session ownership via context.sessionID, pty_read, buffered output, optional pattern matching with ignoreCase, offsets/limits, timeouts converted with input.timeoutSeconds * 1_000, and timeout termination handling where SIGKILL yields PTY output pattern timed out.
• 🟡 (04:02) PTY implementation throws exact errors including PTY Location session limit reached (${MAX_SESSIONS})., Failed to start PTY command: ${input.command}, and PTY command exceeds the ${MAX_ARGUMENTS} argument limit (${args.length} arguments).
• 🟡 (04:02) Running opencode.service process had MainPID=2745754, command /home/byk/.opencode/server/opencode-server --hostname=0.0.0.0 --port=4096, working directory /home/byk/Code, user/group IDs 1000/1000, and start time Tue 2026-09-08 00:33:06 UTC.
• 🟡 (04:02) opencode.service runtime properties were Delegate=no, PrivateTmp=yes, ProtectHome=read-only, ProtectSystem=strict, NoNewPrivileges=yes, RestrictNamespaces=no, and KillMode=control-group.
• 🟡 (04:02) Base unit /etc/systemd/system/opencode.service uses EnvironmentFile=/home/byk/.opencode/env, User=byk, WorkingDirectory=/home/byk/Code, Restart=always, RestartSec=5, Nice=-5, LimitNOFILE=65535, LimitNPROC=4096, MemoryMax=13G, MemoryHigh=12G, NoNewPrivileges=true, ProtectSystem=strict, ProtectHome=read-only, ReadWritePaths=/home/byk, and PrivateTmp=yes.
• 🟡 (04:02) Base /etc/systemd/system/opencode.service defines ExecStart=/home/byk/.opencode/bin/opencode serve --hostname=0.0.0.0 --port=4096, but drop-in /etc/systemd/system/opencode.service.d/10-fossilize-server.conf clears and replaces it with ExecStart=/home/byk/.opencode/server/opencode-server --hostname=0.0.0.0 --port=4096.
• 🟡 (04:02) opencode.service process 2745754 was directly parented by PID 1, had session ID 2745754, and belonged to cgroup 0::/system.slice/opencode.service.
• 🟡 (04:02) For process 2745754, /proc/2745754/ns/pid had inode 4026531836 and /proc/2745754/ns/mnt had inode 4026532315; both namespace handles were owned by uid=0 gid=0 with mode 444.