[PR #1924] [MERGED] add note for 'volatile' storage support #4132

New issue

Closed

opened 2026-05-05 10:14:23 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 10:14:23 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/1924
Author: @ghost
Created: 5/4/2018
Status: ✅ Merged
Merged: 5/8/2018
Merged by: @Fred-Barclay

Base: master ← Head: gnome-logs

📝 Commits (1)

45a817f add note for 'volatile' staorage support

📊 Changes

1 file changed (+3 additions, -1 deletions)

View changed files

📝 etc/gnome-logs.profile (+3 -1)

📄 Description

@Fred-Barclay @SkewedZeppelin Did some further testing, especially when using systemd's volatile storage (which is stored only in memory, i.e. below /run/log/journal). In that case machine-id needs to be added to private-etc, as well as commenting both nogroups and noroot. Realizing this is not a default setup and the release of 0.9.54 is approaching, it's probably better to not mess with nogroups/noroot now. Perhaps adding machine-id to private-etc is not that problematic. Adding a reminder for users who run a volatile storage setup might be doable. Thoughts?

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/1924 **Author:** [@ghost](https://github.com/ghost) **Created:** 5/4/2018 **Status:** ✅ Merged **Merged:** 5/8/2018 **Merged by:** [@Fred-Barclay](https://github.com/Fred-Barclay) **Base:** `master` ← **Head:** `gnome-logs` --- ### 📝 Commits (1) - [`45a817f`](https://github.com/netblue30/firejail/commit/45a817f877d7ed3c8fd2b6a182f245a7ad3cb50f) add note for 'volatile' staorage support ### 📊 Changes **1 file changed** (+3 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `etc/gnome-logs.profile` (+3 -1) </details> ### 📄 Description @Fred-Barclay @SkewedZeppelin Did some further testing, especially when using systemd's `volatile` storage (which is stored only in memory, i.e. below /run/log/journal). In that case `machine-id` needs to be added to private-etc, as well as commenting both `nogroups` and `noroot`. Realizing this is not a default setup and the release of 0.9.54 is approaching, it's probably better to not mess with nogroups/noroot now. Perhaps adding `machine-id` to private-etc is not that problematic. Adding a reminder for users who run a volatile storage setup might be doable. Thoughts? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

gitea-mirror

2026-05-05 10:14:23 -06:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#4132

No description provided.

Rows
Columns