linux observer
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

fix(service): move StartLimit* keys to [Unit] section

Modern systemd (>= 230) requires StartLimitIntervalSec= and
StartLimitBurst= in [Unit]. In [Service] they are silently ignored,
so the observer's restart rate-limit never took effect and an
observer crash loop was not throttled. Reference: systemd.unit(5).

This eliminates the "Unknown key 'StartLimitIntervalSec'" and
"Unknown key 'StartLimitBurst'" warnings emitted by systemd when
loading the unit.

Existing installs pick up the fix on their next `make install-service`
run — no migration logic required.

Out of scope / follow-ups:
- solstone-tmux's unit template has the identical bug (separate lode).
- tests/test_sync.py::TestQuarantineZeroByte::test_zero_byte_segment_quarantined
fails on base as well; unrelated pre-existing mismatch between sync
quarantine cleanup and its test expectations.

Co-Authored-By: OpenAI Codex <codex@openai.com>

+2 -2
+2 -2
src/solstone_linux/solstone-linux.service.in
··· 2 2 Description=Solstone Linux Desktop Observer 3 3 After=graphical-session.target 4 4 BindsTo=graphical-session.target 5 + StartLimitIntervalSec=300 6 + StartLimitBurst=5 5 7 6 8 [Service] 7 9 Type=simple ··· 10 12 Environment=PATH={PATH} 11 13 Restart=on-failure 12 14 RestartSec=10 13 - StartLimitIntervalSec=300 14 - StartLimitBurst=5 15 15 16 16 [Install] 17 17 WantedBy=graphical-session.target