79512625

Date: 2025-03-16 13:45:26
Score: 1
Natty:
Report link

I am the OP of this question. Thank you all for your attention!

I just figured out the reason behind this unexpected behavior. It seems to be related to the Linux kernel configuration -- kernel.shm_rmid_forced. When I changed it with the following command:

sudo sysctl -w kernel.shm_rmid_forced=0

everything started working as expected.

I hope this answer make sense to you!

Reasons:
  • Blacklisted phrase (0.5): Thank you
  • Has code block (-0.5):
  • Self-answer (0.5):
  • Low reputation (0.5):
Posted by: StaY_Hungry