| delorie.com/archives/browse.cgi | search |
| DMARC-Filter: | OpenDMARC Filter v1.4.2 delorie.com 55U9kMJG2720623 |
| Authentication-Results: | delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com |
| Authentication-Results: | delorie.com; spf=pass smtp.mailfrom=cygwin.com |
| DKIM-Filter: | OpenDKIM Filter v2.11.0 delorie.com 55U9kMJG2720623 |
| Authentication-Results: | delorie.com; |
| dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=ZEoskPy+ | |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| DKIM-Filter: | OpenDKIM Filter v2.11.0 sourceware.org BFAE53860007 |
| DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; |
| s=default; t=1751276780; | |
| bh=deUtZJtW94zaxqz8Y+oXc+iq1NQwlwFgymsbIlMIa/A=; | |
| h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: | |
| List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: | |
| From; | |
| b=ZEoskPy+ks5RtlxTKfc5n2EKztxSYKiE+195DS/CJs/Fr6ROEqAlKvXJ+jrImiPjt | |
| x4sqWATKw08l3NWxKAYAlQ283Aq3pt8CzQDa0w3qFVDsDwEJ1lsVFoYoijqhJI8/oK | |
| xk2e4pdYgPNn638t505Yrw716g4s/My4lh/VIQS0= | |
| X-Original-To: | cygwin AT cygwin DOT com |
| Delivered-To: | cygwin AT cygwin DOT com |
| DKIM-Filter: | OpenDKIM Filter v2.11.0 sourceware.org 2D593385212B |
| Date: | Mon, 30 Jun 2025 11:45:54 +0200 |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: setpgid non-compliance with POSIX? |
| Message-ID: | <aGJc0nVQ-1v1DqCO@calimero.vinschen.de> |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| References: | <3391453b-7914-a319-fad8-4729610558ea AT jdrake DOT com> |
| MIME-Version: | 1.0 |
| In-Reply-To: | <3391453b-7914-a319-fad8-4729610558ea@jdrake.com> |
| X-BeenThere: | cygwin AT cygwin DOT com |
| X-Mailman-Version: | 2.1.30 |
| List-Id: | General Cygwin discussions and problem reports <cygwin.cygwin.com> |
| List-Unsubscribe: | <https://cygwin.com/mailman/options/cygwin>, |
| <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe> | |
| List-Archive: | <https://cygwin.com/pipermail/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-request AT cygwin DOT com?subject=help> |
| List-Subscribe: | <https://cygwin.com/mailman/listinfo/cygwin>, |
| <mailto:cygwin-request AT cygwin DOT com?subject=subscribe> | |
| From: | Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com> |
| Reply-To: | cygwin AT cygwin DOT com |
| Cc: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
| Errors-To: | cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com |
| Sender: | "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com> |
On Jun 28 12:32, Jeremy Drake via Cygwin wrote: > I was looking at setpgid yesterday, and it seems deficient with respect to > the errors required to be returned by the POSIX docs in > https://pubs.opengroup.org/onlinepubs/9799919799/functions/setpgid.html > > Basically, it seems that setpgid allows any arbitrary positive integer to > be set as pgid, rather than restricting to setting it to either the > process's pid or to an existing pgid in the same session (sid). Yeah, error checking in setpgid is a bit on the lacking side. With only minor changes, the function is basically 25 years old :} Off the top of my head I don't know how to check the pgid already exists. Do you? Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |