Skip to content
The Chat Archive
command-a-03-2025· Cohere LMArena Human Preference 140K

What are good practices when setting up logs with journald? Group of answer choices Have…

  1. User

    What are good practices when setting up logs with journald? Group of answer choices Have the /var directory on a separate partition or filesystem Create the /var/log/journal directory or change the journald config to Storage=persistent Enable Forward Secure Sealing (FSS) to protect messages submitted to the journal All of the above

  2. Assistant

    The correct answer is: All of the above.

    Here’s why each practice is considered good when setting up logs with journald:

    1. Have the /var directory on a separate partition or filesystem:

      • Isolating /var (where journal logs are stored by default) prevents the root filesystem from filling up due to excessive logging. This ensures system stability and avoids issues like running out of disk space.
    2. Create the /var/log/journal directory or change the journald config to Storage=persistent:

      • By default, systemd-journald uses volatile storage, which is lost on reboot. Setting Storage=persistent in /etc/systemd/journald.conf ensures logs are stored persistently across reboots. Alternatively, creating /var/log/journal manually enables persistent storage.
    3. Enable Forward Secure Sealing (FSS) to protect messages submitted to the journal:

      • FSS cryptographically seals journal entries, ensuring their integrity and preventing tampering. This enhances security and trust in the logged data. Enable it by setting Seal=yes in /etc/systemd/journald.conf.

    Summary of Good Practices:

    • Separate /var partition: Prevents disk space issues.
    • Persistent storage: Ensures logs survive reboots.
    • Forward Secure Sealing: Protects log integrity.

    All of these practices together contribute to a robust and secure logging setup with journald.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.