Open YanjiangChen opened 8 months ago
Thank you for reporting! I will take a look to understand if there is a real issue or not, it could be possible that multiple execve
events are called
The process ID and thread ID of these events are the same, and the exit event is not triggered before a new execve event is started.
Thank you for reporting! I will take a look to understand if there is a real issue or not, it could be possible that multiple
execve
events are called
Have you ever encountered this situation where execve was started multiple times? If so, can you tell me in detail?
I found a new problem. After opening the file in vscode, only the execve event was generated, but no process exit event was generated.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
rule:
events:
...Multiple identical events