<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Linux on My Experiments</title>
    <link>https://myexperiments.blog/tags/linux/</link>
    <description>Recent content in Linux on My Experiments</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>&amp;copy; 2026 Mike</copyright>
    <lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://myexperiments.blog/tags/linux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Upgrading OpenClaw 2026.4.29 → 2026.5.4 (the self-killing gateway mystery)</title>
      <link>https://myexperiments.blog/posts/openclaw-2026-4-29-to-2026-5-4/</link>
      <pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate>
      <guid>https://myexperiments.blog/posts/openclaw-2026-4-29-to-2026-5-4/</guid>
      <description>The upgrade itself worked, but the web UI kept disconnecting because an old root user-level openclaw-gateway.service was still running and fighting the real OpenClaw system service for port 18789. Here’s how we proved it and fixed it.</description>
    </item>
  </channel>
</rss>
