Add autostart package

adds a systemd timer and service and a shell script to call `intelmqctl
start` on system boot and every five minutes

raise debian compat level 10 for better and automatic dh-systemd support
https://wiki.debian.org/Teams/pkg-systemd/Packaging#Using_debhelper_with_dh_systemd

Author: sebix

CHANGELOG.md

@@ -55,6 +55,7 @@ Please refer to the [NEWS](NEWS.md) for a list of changes which have an affect o
 ### Packaging
 - Replace `/opt/intelmq` example paths in bots with variable `VAR_STATE_PATH` for correct paths in LSB-path setups like with packages (PR#2587 by Sebastian Wagner).
 - New deb-package `intelmq-contrib` with all `contrib/` scripts and documentation (PR#2614 by Sebastian Wagner).
+- New deb-package `intelmq-autostart` containing systemd services and timers to start all enabled IntelMQ bots at boot and periodically (PR#2638 by Sebastian Wagner).
 
 ### Tests
 - `intelmq.tests.lib.test_pipeline.TestAmqp.test_acknowledge`: Skip on all Python versions when running on CI (PR#2602 by Sebastian Wagner).

contrib/autostart/intelmq-periodic-start.timer

@@ -0,0 +1,11 @@
+[Unit]
+Description=Periodically start all enabled IntelMQ bots
+
+[Timer]
+# run every 5 minutes
+OnUnitActiveSec=5minutes
+Unit=intelmq-start.service
+Persistent=true
+
+[Install]
+WantedBy=multi-user.target timers.target

contrib/autostart/intelmq-start.service

@@ -0,0 +1,17 @@
+[Unit]
+Description=Start all enabled IntelMQ bots
+After=network.target
+# will be replaced by valkey in next distribution versions
+Requires=redis-server.service
+
+[Service]
+# oneshot does not work as it stops the remaining processes
+Type=simple
+ExecStart=/usr/bin/intelmq-start.sh
+User=intelmq
+Group=intelmq
+RemainAfterExit=yes
+KillMode=process
+
+[Install]
+WantedBy=multi-user.target

contrib/autostart/intelmq-start.sh

@@ -0,0 +1,9 @@
+#!/bin/bash
+
+# suppress stdout output. Errors go to stderr and are kept
+
+if [ "$UID" -eq 0 ]; then
+    sudo -u intelmq intelmqctl start > /dev/null
+else
+    nohup intelmqctl start > /dev/null
+fi

debian/compat

@@ -1 +1 @@
-9
+10

debian/control

@@ -91,3 +91,20 @@ Description: Contributed scripts for IntelMQ
  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  SOFTWARE.
+
+Package: intelmq-autostart
+Architecture: all
+Depends: intelmq,
+         ${misc:Depends},
+         ${python3:Depends}
+Suggests:
+Description: Automatic start for all IntelMQ bots
+ FIXME
+ .
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+ SOFTWARE.

debian/intelmq-autostart.install

@@ -0,0 +1,3 @@
+contrib/autostart/intelmq-periodic-start.timer /lib/systemd/system/
+contrib/autostart/intelmq-start.service /lib/systemd/system/
+contrib/autostart/intelmq-start.sh /usr/bin/

docs/admin/configuration/intelmq.md

@@ -383,10 +383,11 @@ Usually, this configuration doesn't need any change. It is mostly maintained by
 }
 ```
 
+## Automatic start
 
+By default the operating system does not start any IntelMQ bots by itself, they must be started by `intelmqctl start`.
 
+In order to automatically start all enabled bots by default, you can either setup your own job scheduling or use a shorthand:
 
-
-
-
-
+In a package-installation, you can install the package `intelmq-autostart`.
+It calls `intelmqctl start` on system boot after the message queue Redis/Valkey is available and then every five minutes.