https://blog.margrop.net/en/tag/background-service/ Recent content in Background Service on Margrop Blog Hugo -- gohugo.io en-US Sat, 27 Jun 2026 17:12:00 +0800 https://blog.margrop.net/en/post/macos-26-launchdaemon-boot-service-frp-easytier/ Sat, 27 Jun 2026 17:12:00 +0800 https://blog.margrop.net/en/post/macos-26-launchdaemon-boot-service-frp-easytier/ <blockquote> <p><strong>Short version</strong></p> <p>If you want <code>frp</code>, <code>EasyTier</code>, a sync agent, a collector, a bot, or a proxy daemon to start automatically on macOS 26, the key is not “where can I hide this command?” The key is “which native service manager owns its lifecycle?” This article is about unattended background services, not ordinary desktop login apps.</p> <p>On macOS 26, a daemon that must start before user login belongs in /Library/LaunchDaemons. Login items and LaunchAgents are tools opened after a person enters the room. LaunchDaemons are more like the building&rsquo;s elevator or water pump: they should run as the machine comes up.</p> <p>I will show two paths: <strong>manual configuration</strong>, for understanding every moving part, and <strong>agent / one-click automation</strong>, for cases where you already know where the binary and config file live. The scripts are self-contained, use built-in OS mechanisms, do not download third-party wrappers, and do not include real addresses, hostnames, private domains, or secrets.</p> </blockquote> https://blog.margrop.net/en/post/windows-11-10-background-service-autostart-frp-easytier/ Sat, 27 Jun 2026 17:11:00 +0800 https://blog.margrop.net/en/post/windows-11-10-background-service-autostart-frp-easytier/ <blockquote> <p><strong>Short version</strong></p> <p>If you want <code>frp</code>, <code>EasyTier</code>, a sync agent, a collector, a bot, or a proxy daemon to start automatically on Windows 11/10, the key is not “where can I hide this command?” The key is “which native service manager owns its lifecycle?” This article is about unattended background services, not ordinary desktop login apps.</p> <p>On Windows, the first decision is whether the executable is a real Windows Service. Common command-line daemons such as frp and EasyTier are usually better handled by Task Scheduler at system startup, because it is built in and does not require NSSM, WinSW, or another wrapper.</p> <p>I will show two paths: <strong>manual configuration</strong>, for understanding every moving part, and <strong>agent / one-click automation</strong>, for cases where you already know where the binary and config file live. The scripts are self-contained, use built-in OS mechanisms, do not download third-party wrappers, and do not include real addresses, hostnames, private domains, or secrets.</p> </blockquote> https://blog.margrop.net/en/post/ubuntu-2604-systemd-boot-service-frp-easytier/ Sat, 27 Jun 2026 17:10:00 +0800 https://blog.margrop.net/en/post/ubuntu-2604-systemd-boot-service-frp-easytier/ <blockquote> <p><strong>Short version</strong></p> <p>If you want <code>frp</code>, <code>EasyTier</code>, a sync agent, a collector, a bot, or a proxy daemon to start automatically on Ubuntu 26.04, the key is not “where can I hide this command?” The key is “which native service manager owns its lifecycle?” This article is about unattended background services, not ordinary desktop login apps.</p> <p>On Ubuntu 26.04, the standard answer for a background daemon is not a shell startup hack. It is a systemd unit. systemd can wait for the network, start the process before login, collect logs, restart on failure, and stop it in order during shutdown.</p> <p>I will show two paths: <strong>manual configuration</strong>, for understanding every moving part, and <strong>agent / one-click automation</strong>, for cases where you already know where the binary and config file live. The scripts are self-contained, use built-in OS mechanisms, do not download third-party wrappers, and do not include real addresses, hostnames, private domains, or secrets.</p> </blockquote>