This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] posix: New function posix_spawn_file_actions_addchdir_np [BZ #17405]


On 10/31/18 11:03 PM, Rich Felker wrote:
> On Wed, Oct 31, 2018 at 10:03:26PM -0400, Carlos O'Donell wrote:
>> On 10/30/18 1:50 AM, Florian Weimer wrote:
>>> * Carlos O'Donell:
>>>
>>>> On 10/26/18 10:07 AM, Florian Weimer wrote:
>>>>> I'm not adding documentation in this patch because none exists for the
>>>>> posix_spawn functionality.
>>>>
>>>> We can do better though, I'm happy even if we just add the prototypes
>>>> into the manual to give others a place to hang more text in the future.
>>>> The safety notes would be helpful too, is it MT-safe, AS-safe etc.
>>>>
>>>> Would you please take a stab at adding something minimal?
>>>
>>> I don't want to make *any* changes to the manual at this point, sorry.
>>
>> Thanks. I appreciate the direct answer. I will try to take a stab at
>> some initial documentation for posix_spawn and posix_spawnp so that
>> we have somewhere to hang future changes.
>>
>> For example:
>>
>> diff --git a/manual/process.texi b/manual/process.texi
>> index b82b91f9f1..efa0bb8b14 100644
>> --- a/manual/process.texi
>> +++ b/manual/process.texi
>> @@ -34,6 +34,7 @@ primitive functions to do each step individually instead.
>>  * Process Identification::      How to get the process ID of a process.
>>  * Creating a Process::          How to fork a child process.
>>  * Executing a File::            How to make a process execute another program.
>> +* POSIX Spawn::			Combining fork and exec into spawn.
> 
> Maybe it can't be helped, but I feel like this misrepresents and
> de-motivates posix_spawn. Perhaps instead something like "Execute
> another program as a child process without the need to fork".

How about something shorter like:

"Execute a child process without fork"

Does it matter that the underlying implementation may use for?
I'd say, no it doesn't, what we're explaining is that you can
use posix_spawn to start a child process without the need for
you to also call fork or exec. Right?

-- 
Cheers,
Carlos.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]