Hi Theo
> interesting. Yes, msyscall() should probably be in the "stdio" set.
>
> But I've been considering deleting execpromises. It was put in as an
> experiment, and I tried to make code in the base use it. I was unable
> to find great usage cases, and so I am considering deleting it.
Look
interesting. Yes, msyscall() should probably be in the "stdio" set.
But I've been considering deleting execpromises. It was put in as an
experiment, and I tried to make code in the base use it. I was unable
to find great usage cases, and so I am considering deleting it.
Andrea Biscuola wrote:
Hi @misc
It appear the introduction of msyscall(2), broke the existing code
of one of my projects.
My code use a fork+exec model for executing different commands
and pledge(2) is used for restricting the behavior of the child
process using the execpromises argument.
The problem is that, when a c
3 matches
Mail list logo
