firewalla-snmp-proxy 2.2.2__tar.gz → 2.2.3__tar.gz

{firewalla_snmp_proxy-2.2.2 → firewalla_snmp_proxy-2.2.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: firewalla-snmp-proxy
-Version: 2.2.2
+Version: 2.2.3
 Summary: Monitor a Firewalla Switch over SNMP with any monitoring system
 Author: Kristian Desch
 License: MIT
@@ -109,7 +109,10 @@ sudo ln -sf /opt/firewalla-snmp-proxy-venv/bin/firewalla-snmp-proxy /usr/local/b
 ```
 
 Step 4 binds no sockets, so it is safe to run while something else is already
-listening on the port.
+listening on the port. Step 5 runs in the foreground, which is what you want
+while trying it out — for anything permanent see
+[Install as a service](#install-as-a-service), which restarts on failure and
+survives a reboot.
 
 Then, from anywhere that can reach the proxy:
 
@@ -127,12 +130,29 @@ another host.
 
 ### Install as a service
 
-From the same clone:
+You almost certainly want this. Running `run` in a shell means it dies with
+your session and does not come back after a reboot; a monitoring source that
+quietly stops is worse than one that was never there.
+
+**Install the binary system-wide first.** The generated unit sets
+`ProtectHome=yes`, so systemd cannot execute anything under `/home` or `/root`
+— a per-user `pipx install` produces a binary the service is unable to start,
+even though it runs fine from your shell:
+
+```bash
+pipx uninstall firewalla-snmp-proxy        # if you installed it as yourself
+sudo pipx --global install firewalla-snmp-proxy
+```
+
+Then, from a clone of this repo (for `install.sh` itself):
 
 ```bash
 sudo ./install.sh --service          # or: --service --user snmpproxy
 ```
 
+`install.sh` refuses to proceed with a home-directory binary rather than
+writing a unit that cannot start.
+
 The systemd unit is **generated** from the detected binary path, service user
 and config location — there is nothing to hand-edit. It creates a locked-down
 `firewalla-snmp-proxy` system user, a 0640 root-owned environment file for your

{firewalla_snmp_proxy-2.2.2 → firewalla_snmp_proxy-2.2.3}/README.md

@@ -83,7 +83,10 @@ sudo ln -sf /opt/firewalla-snmp-proxy-venv/bin/firewalla-snmp-proxy /usr/local/b
 ```
 
 Step 4 binds no sockets, so it is safe to run while something else is already
-listening on the port.
+listening on the port. Step 5 runs in the foreground, which is what you want
+while trying it out — for anything permanent see
+[Install as a service](#install-as-a-service), which restarts on failure and
+survives a reboot.
 
 Then, from anywhere that can reach the proxy:
 
@@ -101,12 +104,29 @@ another host.
 
 ### Install as a service
 
-From the same clone:
+You almost certainly want this. Running `run` in a shell means it dies with
+your session and does not come back after a reboot; a monitoring source that
+quietly stops is worse than one that was never there.
+
+**Install the binary system-wide first.** The generated unit sets
+`ProtectHome=yes`, so systemd cannot execute anything under `/home` or `/root`
+— a per-user `pipx install` produces a binary the service is unable to start,
+even though it runs fine from your shell:
+
+```bash
+pipx uninstall firewalla-snmp-proxy        # if you installed it as yourself
+sudo pipx --global install firewalla-snmp-proxy
+```
+
+Then, from a clone of this repo (for `install.sh` itself):
 
 ```bash
 sudo ./install.sh --service          # or: --service --user snmpproxy
 ```
 
+`install.sh` refuses to proceed with a home-directory binary rather than
+writing a unit that cannot start.
+
 The systemd unit is **generated** from the detected binary path, service user
 and config location — there is nothing to hand-edit. It creates a locked-down
 `firewalla-snmp-proxy` system user, a 0640 root-owned environment file for your

{firewalla_snmp_proxy-2.2.2 → firewalla_snmp_proxy-2.2.3}/firewalla_snmp_proxy/__init__.py

@@ -5,4 +5,4 @@ API as a standards-compliant SNMP agent, so any SNMP monitoring system can
 poll a switch that has no SNMP agent of its own.
 """
 
-__version__ = "2.2.2"
+__version__ = "2.2.3"

{firewalla_snmp_proxy-2.2.2 → firewalla_snmp_proxy-2.2.3}/firewalla_snmp_proxy.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: firewalla-snmp-proxy
-Version: 2.2.2
+Version: 2.2.3
 Summary: Monitor a Firewalla Switch over SNMP with any monitoring system
 Author: Kristian Desch
 License: MIT
@@ -109,7 +109,10 @@ sudo ln -sf /opt/firewalla-snmp-proxy-venv/bin/firewalla-snmp-proxy /usr/local/b
 ```
 
 Step 4 binds no sockets, so it is safe to run while something else is already
-listening on the port.
+listening on the port. Step 5 runs in the foreground, which is what you want
+while trying it out — for anything permanent see
+[Install as a service](#install-as-a-service), which restarts on failure and
+survives a reboot.
 
 Then, from anywhere that can reach the proxy:
 
@@ -127,12 +130,29 @@ another host.
 
 ### Install as a service
 
-From the same clone:
+You almost certainly want this. Running `run` in a shell means it dies with
+your session and does not come back after a reboot; a monitoring source that
+quietly stops is worse than one that was never there.
+
+**Install the binary system-wide first.** The generated unit sets
+`ProtectHome=yes`, so systemd cannot execute anything under `/home` or `/root`
+— a per-user `pipx install` produces a binary the service is unable to start,
+even though it runs fine from your shell:
+
+```bash
+pipx uninstall firewalla-snmp-proxy        # if you installed it as yourself
+sudo pipx --global install firewalla-snmp-proxy
+```
+
+Then, from a clone of this repo (for `install.sh` itself):
 
 ```bash
 sudo ./install.sh --service          # or: --service --user snmpproxy
 ```
 
+`install.sh` refuses to proceed with a home-directory binary rather than
+writing a unit that cannot start.
+
 The systemd unit is **generated** from the detected binary path, service user
 and config location — there is nothing to hand-edit. It creates a locked-down
 `firewalla-snmp-proxy` system user, a 0640 root-owned environment file for your

{firewalla_snmp_proxy-2.2.2 → firewalla_snmp_proxy-2.2.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "firewalla-snmp-proxy"
-version = "2.2.2"
+version = "2.2.3"
 description = "Monitor a Firewalla Switch over SNMP with any monitoring system"
 readme = "README.md"
 requires-python = ">=3.9"