On Sat, Jan 09, 2021 at 08:25:46PM +0300, Vasily Postnicov wrote:
> Brilliant! It took me almost a day to dive into ZeroMQ to reassure
> myself that there is nothing wrong with it. When I tried to write
> minimal test programs which call fork after pthread_create() in all
> combinations. When I rea
Oh, I almost forgot. I am on f2b794e now
сб, 9 янв. 2021 г. в 20:25, Vasily Postnicov :
>
> Brilliant! It took me almost a day to dive into ZeroMQ to reassure
> myself that there is nothing wrong with it. When I tried to write
> minimal test programs which call fork after pthread_create() in all
>
Brilliant! It took me almost a day to dive into ZeroMQ to reassure
myself that there is nothing wrong with it. When I tried to write
minimal test programs which call fork after pthread_create() in all
combinations. When I realized that NSS stub module is what I need.
Instructions:
1) Compile NSS
On Sat, Jan 09, 2021 at 04:16:49PM +0300, Vasily Postnicov wrote:
> Turns out, if you do not specify either -4 or -6 to ping, unsandboxed
> getaddrinfo() will be called in /usr/src/sbin/ping/main.c, line 139.
> (what's the point in sandboxing then, lol?) This somehow affects
> sandboxing.
Indeed,
Turns out, if you do not specify either -4 or -6 to ping, unsandboxed
getaddrinfo() will be called in /usr/src/sbin/ping/main.c, line 139.
(what's the point in sandboxing then, lol?) This somehow affects
sandboxing.
Look at the screenshot, it explains where fork() gets stuck.
https://photos.app.go
