On Mon, May 6, 2024 at 3:22 PM Mauro Tridici <mauro.trid...@cmcc.it> wrote: : > checking the operating system (CentOS 7.2) audit logs, I detect a lot of > "sleep command memory violation". > I investigated about this issue for almost a week and I think I found the > cause of the error message mentioned above. > It seems it is related to the "parallel" command usage and I'm able to > replicate the problem as follows. > > Could you please help me to understand what I'm doing wrong and how to fix > this issue?
I tested with https://app.vagrantup.com/Gigasavvy/boxes/centos7-LAMP and cannot reproduce the problem. Please follow https://www.gnu.org/software/parallel/man.html#bug-dependent-on-environment > type=ANOM_ABEND msg=audit(1714688507.057:173872): auid=0 uid=0 gid=0 > ses=23831 pid=74652 comm="sleep" reason="memory violation" sig=11 This smells like `sleep` is doing a memory violation - so not an issue with GNU Parallel. But it might be that GNU Parallel triggers this. GNU Parallel calls `sleep` during startup. A wild guess is that the specific binary of `sleep` that you have installed for some odd reason crashes when called from GNU Parallel. All of this is easier to verify if you follow https://www.gnu.org/software/parallel/man.html#bug-dependent-on-environment /Ole
