Configure journald to store persistent data under /var/log/journal when possible.
Which setting is appropriate?
Storage=persistent requests persistent journal storage; volatile uses /run and disappears across reboot.
Detailed explanation
Storage=volatileIncorrect. volatile stores the journal in temporary runtime storage.
Incorrect. volatile stores the journal in temporary runtime storage.
Storage=noneIncorrect. none disables journal storage.
Incorrect. none disables journal storage.
Storage=persistentCorrect. persistent stores the journal under /var/log/journal.
Correct. persistent stores the journal under /var/log/journal.
ForwardToSyslog=persistentIncorrect. ForwardToSyslog is a boolean forwarding setting, not a storage mode.
Incorrect. ForwardToSyslog is a boolean forwarding setting, not a storage mode.
Try it yourself
An example you can run in a temporary verification environment.
systemd-analyze cat-config systemd/journald.conf 2>/dev/null | grep -E '^Storage=' | tail -n 1 || trueExpected result
明示設定があればStorage=...。未設定なら空出力で既定動作Key points
- persistent uses /var/log
- volatile uses /run
- Restart or reload may be needed
Notes
- Environment: systemd-analyzeによる設定読取のみ
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.