RE: system() and pthread_atfork()

2020-01-13 Thread Karstens, Nate
s, Nate -Original Message- From: Robert Elz Sent: Monday, January 13, 2020 6:43 AM To: Schwarz, Konrad Cc: Karstens, Nate ; austin-group-l@opengroup.org Subject: Re: system() and pthread_atfork() CAUTION - EXTERNAL EMAIL: Do not click any links or open any attachments unless you trust th

Re: system() and pthread_atfork()

2020-01-12 Thread Karstens, Nate
have also been in contact with the author of the original FD_CLOFORK patch for Linux and they are OK with me taking that over and updating for the latest kernel. Cheers, Nate -Original Message- From: Karstens, Nate Sent: Friday, December 20, 2019 4:40 PM To: austin-group-l@opengroup.org

Re: system() and pthread_atfork()

2019-12-20 Thread Karstens, Nate
Thanks to everyone for the great responses! Below are some notes/discussion on the various replies I've seen: > If it's supposed to behave as if fork() has been called, this implicitly > includes calling atfork handlers when POSIX_C_SOURCE is defined... Regarding glibc, I'm not sure the

system() and pthread_atfork()

2019-12-18 Thread Karstens, Nate
Greetings, The current definition of system() does not define if the pthread_atfork() handlers are called. We ran into a scenario where this caused a problem and wanted to share it with the mailing list to better understand why those handlers are not required and get some advice on how best to