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

sediff reported "Killed" #144

Open
pengshanyu opened this issue Dec 13, 2024 · 1 comment
Open

sediff reported "Killed" #144

pengshanyu opened this issue Dec 13, 2024 · 1 comment

Comments

@pengshanyu
Copy link

Hi,
When I run sediff to check the difference of two SELinux policy files, I did not specify any expression, because I'd like to check all supported policy elements. But the following command does not work for me.

# sediff /etc/selinux/targeted/policy/policy.33 /sys/fs/selinux/policy
Killed 

It seems that this command took too long and was terminated. Could someone give me some help please? Thanks.

@pebenito
Copy link
Member

pebenito commented Jan 6, 2025

sediff is extremely resource intensive when you compare rules. Please check dmesg to see if it was killed by OOM. If there are large numbers of rules, such as in a policy with unconfined, sediff can easily need 15GB-20GB memory.

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

No branches or pull requests

2 participants