Service Deployment Notes¶
Offline mode can be run interactively or adapted to a long-running Linux service deployment.
Recommended Bring-Up Pattern¶
- Validate the configuration.
- Run in the foreground first.
- Confirm logs and NDJSON output.
- Move to a service-style deployment after behavior is stable.
Existing Service Assets¶
The repo already contains Linux service and packaging assets, including:
systemd/pqc-sniffer.servicepackaging/systemd/pqc-sniffer.servicescripts/install.shpackaging/build-rpm.sh
Important Note¶
This site is still offline-mode focused. It does not attempt to fully document every packaging and service-install path in the repo. Instead, it gives operators the minimum context needed to understand how offline mode fits into a managed Linux deployment.
Practical Advice¶
- Keep
logging.database.enabled: falsein offline-only deployments. - Validate output paths before running under systemd.
- Confirm file permissions for both the log file and NDJSON destination.
- Verify rotation settings early so retention matches operator expectations.