Re: [Tarantool-patches] [PATCH 6/7] popen: handle setsid os specifics

[Cyrill Gorcunov <gorcunov@gmail.com>]

On Tue, Mar 03, 2020 at 02:38:53PM +0300, Alexander Turenko wrote:
> On Mon, Mar 02, 2020 at 11:12:26PM +0300, Cyrill Gorcunov wrote:
> > On linux it is fine to call setsid right after
> > the vfork, in turn on bsd pgrp should be used.
> 
> Can you refer a source of this information?
> 
> I tried the following snippet on Mac OS and FreeBSD and it at least does
> not report an error:
> 
>  | #include <unistd.h>
>  | #include <stdio.h>
>  | 
>  | int
>  | main()
>  | {
>  | 	if (setsid() == -1) {
>  | 		perror("setsid");
>  | 		return 1;
>  | 	}
>  | 	return 0;
>  | }
> 
> $ cc setsid.c -o setsid
> $ echo 1 | ./setsid
> 
> (Pipeline is to not be a session leader already, this will lead to EPERM.)

I found that people are hitting the same problem.
https://stackoverflow.com/questions/15179361/setpgrp-setpgid-fails-works-on-mac-osx-not-on-linux

The main problem is that I don't have a clue about macos internals
but it looks like we have to setup group instead. To me it is
vague area. I suspect it is due to vfork macos specifics.