Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lib/deploy: Log SELinux policy refresh #3081

Merged
merged 1 commit into from Oct 20, 2023

Conversation

jlebon
Copy link
Member

@jlebon jlebon commented Oct 19, 2023

I have a suspicion that the semodule -N --refresh we do here is involved in coreos/fedora-coreos-tracker#1597. Let's log when we execute it and include its time.

While we're here, also log the time it takes to syncfs() and the fsfreeze/thaw cycling. It's logged in a structured journal entry, but that's less accessible than just having it in the journal message field.

I have a suspicion that the `semodule -N --refresh` we do here is
involved in coreos/fedora-coreos-tracker#1597.
Let's log when we execute it and include its time.

While we're here, also log the time it takes to `syncfs()` and the
fsfreeze/thaw cycling. It's logged in a structured journal entry, but
that's less accessible than just having it in the journal message field.
Comment on lines +1654 to +1655
ot_journal_print (LOG_INFO, "Completed syncfs() for system root in %" G_GUINT64_FORMAT " ms",
end_msec - start_msec);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is completely fine but I previously changed it because in the end the journal keeps timestamps so one can just diff those to see.

@cgwalters cgwalters merged commit 98f1501 into ostreedev:main Oct 20, 2023
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants