Prevent double logging by journald and rsyslogd

Using the autoinstaller does not prevent journald to write the persistant system journal which is not needed as rsyslogd manages the log as discussed in the forum.

● systemd-journald.service - Journal Service
     Loaded: loaded (/lib/systemd/system/systemd-journald.service; static)
     Active: active (running) since Wed 2023-09-06 09:34:49 CEST; 11min ago
TriggeredBy: ● systemd-journald-dev-log.socket
             ● systemd-journald.socket
             ● systemd-journald-audit.socket
       Docs: man:systemd-journald.service(8)
             man:journald.conf(5)
   Main PID: 245 (systemd-journal)
     Status: "Processing requests..."
      Tasks: 1 (limit: 2265)
     Memory: 10.6M
        CPU: 142ms
     CGroup: /system.slice/systemd-journald.service
             └─245 /lib/systemd/systemd-journald

Sep 06 09:34:49 debian systemd-journald[245]: Journal started
Sep 06 09:34:49 debian systemd-journald[245]: Runtime Journal (/run/log/journal/dfe13fb75449491c845f0a302341af58) is 2.4M, max 19.3M, 16.9M free.
Sep 06 09:34:49 debian systemd-journald[245]: Time spent on flushing to /var/log/journal/dfe13fb75449491c845f0a302341af58 is 196.341ms for 1468 entries.
Sep 06 09:34:49 debian systemd-journald[245]: System Journal (/var/log/journal/dfe13fb75449491c845f0a302341af58) is 20.5M, max 4.0G, 3.9G free.
Sep 06 09:34:49 debian systemd-journald[245]: Received client request to flush runtime journal.

The merge request disables the persistent system journal of journald.

Edited by Dr. Yves Kreis
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information